Conditional message forwarding functions

ABSTRACT

Systems, methods, and devices that can conditionally and/or automatically control message forwarding by communication devices are presented. A network message management component and/or handset message management component can monitor messages (e.g., short message service (SMS) messages) communicated between user equipment (UE) in a communication network, identify and/or intercept a message for which one or more forwarding conditions have been specified by the message originator, target, or forward target, and conditionally and/or automatically route the message to the target and/or forward target in accordance with predefined message routing rules based at least in part on the conditions specified by the originator, target, or forward target. The predefined message routing rules can be implemented by the network and/or the UEs, and can relate to the UE identifiers, time, priority, cost, operation state, size, desired automatic response messages, or other desired factors, associated with the message.

TECHNICAL FIELD

The subject specification generally relates to wireless communications,and, more particularly, to systems, methods, and devices forimplementing network-based and/or handset-based conditional messageforwarding functions.

BACKGROUND

Mobile communication devices, such as cellular phones, have becomeprevalent in everyday life. The use of such devices for messaging (e.g.,text messages (e.g., short message service (SMS), enhanced messageservice (EMS)), multimedia messages (e.g., multimedia messaging service(MMS)), instant messages, Session Initiation Protocol (SIP) messages,etc.) is ever increasing. Some users have unlimited messaging plans,whereby such users are allowed to send or receive an unlimited number ofmessages over a billing period for a specified fee. However, other usershave limited messaging plans, whereby such users pay a certain fee for aspecified number of messages per billing period and pay an additionalfee per message for each message over the specified number of messages.Still other users have no messaging plan, whereby such users pay aspecified fee for each message sent or received during the billingperiod.

Messaging using communication devices has increased in popularity inrecent years. Sometimes, when a message (e.g., SMS message) is sent froman originating communication device to a target communication device,the target user associated with the target communication device canprefer that the message be forwarded to another communication device,which can be associated with the target user or another user for whichthe target user desires to forward the message. However, conventionally,the technologies for forwarding messages, such as SMS messages, remainrelatively primitive, and most message forwarding functions are onlyimplemented on the communication device and not in the network. Onedrawback with only employing message forwarding functions on thecommunication device is that such message forwarding functions do notwork when the communication device is turned off.

One network-based SMS message forwarding technology uses a Home LocationRegistrar (HLR) proxy to intercept an SMS message to verify whether themessage needs to be forwarded to another communication device. However,this network-based SMS message forwarding technology limits itself to anunconditional forwarding mode which means that if the target user electsto forward an SMS message to another communication device, the SMSmessage will be forwarded immediately, even if the originating user thatsent the SMS message does not desire to have the message forwardedand/or the other user to which the message was forwarded does not desireto receive the message being forwarded. Such unconditional forwarding ofSMS messages can result in potentially sensitive information in the SMSmessage being forwarded to another user, even if the originating useronly desires the target user to be able to view the message and does notdesire other persons, like the other user, to receive and view themessage, and/or can result in the recipient of the forwarded messageincurring the cost of receiving the forwarded message even if therecipient does not desire to receive the forwarded message. Accordingly,today, there is no way to desirably control forwarding of messages tocommunication devices.

The above-described deficiencies of today's messaging systems are merelyintended to provide an overview of some of the problems of conventionalsystems, and are not intended to be exhaustive. Other problems with thestate of the art and corresponding benefits of some of the variousnon-limiting embodiments may become further apparent upon review of thefollowing detailed description.

SUMMARY

The following presents a simplified summary of the various embodimentsin order to provide a basic understanding of some aspects describedherein. This summary is not an extensive overview of the disclosedsubject matter. It is intended to neither identify key or criticalelements of the disclosed subject matter nor delineate the scope of thesubject embodiments. Its sole purpose is to present some concepts of thedisclosed subject matter in a simplified form as a prelude to the moredetailed description that is presented later.

Systems, methods, and devices that can conditionally control messageforwarding by communication devices are presented. A network (NW)message management component and/or handset message managementcomponent(s) (e.g., local or user equipment (UE) message managementcomponent) can monitor messages (e.g., text messages (e.g., shortmessage service (SMS), enhanced message service (EMS)), multimediamessages (e.g., multimedia messaging service (MMS)), instant messages,Session Initiation Protocol (SIP) messages, etc.) communicated betweenUEs (e.g., mobile communication devices, landline communication deviceswith text or mobile messaging capabilities, etc.) in a communicationnetwork, identify and/or intercept a message(s) for which one or moreforwarding conditions have been specified by the sender (e.g.,originating UE or associated originating UE user), intended recipient(e.g., target UE or associated target UE user), or forward recipient(e.g., forward target UE or associated forward target UE user to whichthe intended recipient desires to forward a message that is originallysent from the sender's UE to the intended recipient's UE), and route themessage(s) to the intended recipient and/or intended forward recipientin accordance with predefined message routing rules (e.g., predefinedmessage forwarding rules) and/or message forwarding indicatorsassociated with a message(s), based at least in part on the conditionsspecified by the sender, intended recipient, or intended forwardrecipient. The predefined message forwarding rules can be implemented bythe network and/or the UEs, and can relate to the UE identifiers, time amessage is sent, priority of a message, message cost, UE operationstate, size of a message, desired automatic response messages, or otherdesired factors, associated with the message.

The UE users can select desired message routing rules and other optionsusing their respective UEs or other desired communication devices,wherein their respective message routing rules or other options selectedby the respective UE users and/or other desired information can bestored in respective user profiles of the respective UE users. The userprofiles can be stored in a data store associated with the NW messagemanagement component and/or respective user profiles can be stored inrespective data stores associated with respective handset messagemanagement components in the respective UEs.

When a message is being sent from an originating UE to a target UE, andthe target UE user has set a message routing rule requesting thatmessages (e.g., messages sent to the target UE from the originating UE)be forwarded to a forward target UE, the applicable message managementcomponent(s) (e.g., NW message management component(s) and/or a handsetmessage management component(s)) can analyze the message (e.g., toidentify the originating UE and target UE, identify whether there is amessage-forwarding-allowance indicator and/or the value of suchindicator, identify other characteristics of the message (e.g., size ofthe message, time of the message, whether the message includes anattachment, etc.)), user profiles of the originating UE user, target UEuser, and/or forward target UE user, and/or other information. Theapplicable message management component can apply the applicable messagerouting rules and logic to the message to determine whether the messageis to be forwarded to the forward target UE or not.

For instance, if a message routing rule is set for a target UErequesting that messages sent to the target UE from an originating UE(s)are to be forwarded to a forward target UE, the applicable messagemanagement component can apply that message routing rule, and if thereis no other message routing rule(s) that supercedes that message routingrule, the applicable message management component can forward themessage(s) from an originating UE(s) to the forward target UE. If amessage routing rule(s) and/or message-forwarding-allowance indicator(e.g., set to prohibit forwarding) specified by an originating UEprohibits forwarding the message (e.g., forwarding the message to theforward target UE or a global restriction on message forwarding), and/ora message routing rule(s) specified by the forward target UE prohibitsreceiving the message (e.g., prohibits receiving a forwarded message(s),prohibits receiving a message(s) from the originating UE, and/orprohibits receiving a message(s) forwarded from the target UE, etc.),the applicable message management component (e.g., NW message managementcomponent) can apply the applicable rules and logic and can determinethat the message is not to be forwarded to the forward target UE, eventhough the target UE (or associated target UE user) requested that themessage be forwarded.

In accordance with other aspects, an applicable message managementcomponent(s) can be employed to enable a UE (or associated UE user) toconditionally generate and send (e.g., automatically generate and send)a desired automatic response message in response to a message receivedby the UE, in accordance with applicable message routing rules (e.g., ascontained in user profiles of the originating UE user, target UE userand/or forward target UE user) and/or automatic-message-allowanceindicator (e.g., if any such indicator is employed, or in accordancewith the specified value of such indicator), wherein such indicator canbe added to the message on a per-message basis or added to all messages,as desired by the UE user (e.g., originating UE user sending themessage). When a message is sent from a sending UE to a recipient UE(e.g., sent from an originating UE to a target UE, sent from anoriginating UE to a target UE and/or a forward target UE (e.g., due toconditional message forwarding), or sent from or on behalf of a targetUE to the forward target UE (e.g., due to conditional messageforwarding)), if there is a message routing rule for the recipient UE(e.g., in the associated user profile) that requests to send anautomatic response message to the sending UE, the applicable messagemanagement component can analyze the message (e.g., to identify a valueof an automatic-response-allowance indicator) and/or user profileassociated with the sending UE (e.g., to identify whether there is amessage routing rule that prohibits automatic response messages beingsent to or received by the sending UE), and applying the applicablemessage routing rules and logic, can determine whether the automaticresponse message can be sent (e.g., automatically) to the sending UEfrom the recipient UE. For example, if the user profile associated withthe sending UE contains a message routing rule that prohibits theautomatic response message from being sent to or received by the sendingUE, and/or the message, which was sent by the sending UE to therecipient UE, includes an automatic-response-allowance indicator that isset to prohibit the automatic response message from being sent to orreceived by the sending UE, the applicable message management componentdetermine that no automatic response message is to be sent to thesending UE from the recipient UE, even though the recipient UE desiresto send an automatic response message.

In yet another aspect, the UE can access the applicable messagemanagement component(s) to facilitate using the UE to generate a desiredpreconfigured automatic response message (e.g., from a set ofpreconfigured automatic response messages stored in the data store) or acustom automatic response message. In still another aspect, the UE canemploy the applicable message management component(s) to facilitatecontrolling the timing of sending of the automatic response message, sothat the automatic response message can be sent at a desired time.

The following description and the annexed drawings set forth in detailcertain illustrative aspects of the disclosed subject matter. Theseaspects are indicative, however, of but a few of the various ways inwhich the principles of the various embodiments may be employed and thedisclosed subject matter is intended to include all such aspects andtheir equivalents. Other advantages and distinctive features of thedisclosed subject matter will become apparent from the followingdetailed description of the various embodiments when considered inconjunction with the drawings.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of an example system that can conditionallyforward messages in accordance with various aspects and embodiments ofthe disclosed subject matter.

FIG. 2 depicts a block diagram of an example system that canconditionally forward messages in accordance with aspects andembodiments of the disclosed subject matter.

FIG. 3 illustrates a block diagram of another example system that canconditionally forward messages in accordance with aspects andembodiments of the disclosed subject matter.

FIG. 4 depicts a block diagram of an example network message managementcomponent in accordance with an aspect of the disclosed subject matter.

FIG. 4 illustrates a block diagram of an example mobile device inaccordance with an embodiment of the disclosed subject matter.

FIG. 5 depicts a block diagram of an example handset message managementcomponent in accordance with an embodiment of the disclosed subjectmatter.

FIG. 6 illustrates a block diagram of an example user equipment (UE) inaccordance with an aspect of the disclosed subject matter.

FIG. 7 illustrates a block diagram of an example access point (ΔP) inaccordance with an aspect of the disclosed subject matter.

FIG. 8 illustrates a flowchart of an example method for conditionalforwarding of messages in accordance with various aspects andembodiments of the disclosed subject matter.

FIG. 9 depicts a flowchart of an example method that can conditionallyforward messages in accordance with various aspects of the disclosedsubject matter.

FIG. 10 illustrates a flowchart of an example method that can employ oneor more message routing rules or messaging options to facilitateconditional forwarding of messages in accordance with aspects of thedisclosed subject matter.

FIG. 11 depicts a flowchart of an example method that can conditionallysend an automatic response message in response to a received message inaccordance with aspects of the disclosed subject matter.

DETAILED DESCRIPTION

The disclosed subject matter is described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the various embodiments of the subjectdisclosure. It may be evident, however, that the disclosed subjectmatter may be practiced without these specific details. In otherinstances, well-known structures and devices are shown in block diagramform in order to facilitate describing the various embodiments herein.

As used in this application, the terms “component,” “system,”“interface,” “module,” and the like can refer to a computer-relatedentity or an entity related to an operational machine with one or morespecific functionalities. The entities disclosed herein can be eitherhardware, a combination of hardware and software, software, or softwarein execution. For example, a component may be, but is not limited tobeing, a process running on a processor, a processor, an object, anexecutable, a thread of execution, a program, and/or a computer. By wayof illustration, both an application running on a server and the servercan be a component. One or more components may reside within a processand/or thread of execution and a component may be localized on onecomputer and/or distributed between two or more computers. Also, thesecomponents can execute from various computer readable media havingvarious data structures stored thereon. The components may communicatevia local and/or remote processes such as in accordance with a signalhaving one or more data packets (e.g., data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network such as the Internet with other systemsvia the signal).

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment,” “mobile station,” “mobile,”“subscriber station,” “communication device,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice (e.g., cellular phone, smart phone, computer, personal digitalassistant (PDA), set-top box, Internet Protocol Television (IPTV),electronic gaming device, multi-media recorder/player, videorecorder/player, audio recorder/player, printer, etc.) utilized by asubscriber or user of a wireless communication service to receive orconvey data, control, voice, video, sound, gaming, or substantially anydata-stream or signaling-stream, or, in an embodiment, a wired (e.g.,landline) communication device that has mobile messaging functionalityand is utilized by a subscriber to receive or convey data, control,voice, video, sound, gaming, or substantially any data-stream orsignaling-stream. The foregoing terms are utilized interchangeably inthe subject specification and related drawings. Likewise, the terms“access point,” “base station,” “Node B,” “evolved Node B,” “home Node B(HNB),” “femto access point,” “femtocell,” “pico access point,”“picocell,” and the like, are utilized interchangeably in the subjectapplication, and refer to a wireless network component or appliance thatserves and receives data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream from a set ofsubscriber stations. Data and signaling streams can be packetized orframe-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” and the likeare employed interchangeably throughout the subject specification,unless context warrants particular distinction(s) among the terms.

The following abbreviations are relevant to the subject specification.

2G Second Generation

3G Third Generation

3GPP Third Generation Partnership Project

4G Fourth Generation

AGPS Assisted GPS

AP Access Point

ADSL Asymmetric Digital Subscriber Line

AWS Advanced Wireless Services

BRAS Broadband Remote Access Server

BTA Basic Trading Area

CDMA Code Division Multiple Access

CN Core Network

CS Circuit-Switched

CSCF Call Session Control Function

CPE Customer Premise Equipment

CPN Customer Premise Network

DHCP Dynamic Host Configuration Protocol

DSL Digital Subscriber Line

DSLAM Digital Subscriber Line Access Multiplexer

E911 Enhanced 911

FCC Federal Communications Commission

FL Forward Link

GGSN Gateway GPRS Service Node

GPRS General Packet Radio Service

GPS Global Positioning System

GW Gateway

HAP Home Access Point

HSS Home Subscriber Server

ISDN Integrated Services Digital Network

UE User Equipment

UTRAN Universal Terrestrial Radio Access Network

IMS IP Multimedia Subsystem

IP Internet Protocol

ISP Internet Service Provider

MSA Metropolitan Statistical Areas

MSISDN Mobile Subscriber ISDN Number

MTA Major Trading Areas

NAT Network Address Translation

NTP Network Time Protocol

O&M Operation and Maintenance

PC Personal Computer

PCS Personal Communications Service

PS Packet-Switched

PSTN Public Switched Telephone Network

RAN Radio Access Network

RBS Radio Base Station

RL Reverse Link

RNC Radio Network Controller

RSA Rural Service Area

SGSN Serving GPRS Support Node

SIP Session Initiation Protocol

USSD Unstructured Supplementary Service Data

VPN Virtual Private Network

WAP Wireless Application Protocol

WCDMA Wideband CDMA

XDSL Asynchronous-DSL or Synchronous-DSL

Messaging using communication devices has increased in popularity inrecent years. Sometimes, when a message (e.g., SMS message) is sent froman originating user equipment (UE) to a target UE, the target UE userassociated with the target UE can or may prefer that the message beforwarded to another UE (which also can be referred to as a forwardtarget UE), which can be associated with the target UE user or anotherUE user for which the target UE user desires to forward the message.However, conventionally, the technologies for forwarding messages, suchas SMS messages, remain relatively primitive, and most messageforwarding functions are only implemented on the UE and not in thenetwork. One drawback with only employing message forwarding functionson the UE is that such message forwarding functions do not work when theUE is turned off.

Further, conventional network-based SMS message forwarding technologylimits itself to an unconditional forwarding mode which means that ifthe target UE user elects to forward an SMS message to another UE, theSMS message will be forwarded immediately, even if the originating UEuser that sent the SMS message does not desire to have the messageforwarded and/or the other user (e.g., forward target UE user) to whichthe message was forwarded does not desire to receive the message beingforwarded. Such unconditional forwarding of SMS messages can result inpotentially sensitive information in the SMS message being forwarded toanother UE user, even if the originating UE user only desires the targetUE user to be able to view the message and does not desire otherpersons, like the other UE user, to receive and view the message, and/orcan result in the recipient of the forwarded message incurring the costof receiving the forwarded message even if the recipient does not desireto receive the forwarded message. Accordingly, today, there is no way todesirably control forwarding of messages to communication devices.

To that end, systems, methods, and devices that can conditionally and/orautomatically control message forwarding by communication devices arepresented. A network message management component and/or handset messagemanagement component can monitor messages (e.g., short message service(SMS) messages) communicated between UEs in a communication network,identify and/or intercept a message for which one or more forwardingconditions have been specified by the message originator, target, orforward target, and conditionally and/or automatically route the messageto the target and/or forward target, and/or other desired destination(e.g., message box associated with the target, or message box associatedwith the forward target) in accordance with predefined message routingrules, which can be set in accordance with the conditions specified bythe originator, target, or forward target, and/or other information(e.g., message-forwarding-allowance indicator). The predefined messagerouting rules can be implemented by the network (e.g., employing anetwork message management component) and/or the UEs (e.g., employingrespective handset message management components), and can relate to,for example, the UE identifiers, time, priority, cost, operation state,size, desired automatic response messages, or other desired factors,associated with a message.

In another aspect, in response to a recipient UE receiving a messagefrom a sending UE, an automated response message can be conditionallygenerated and sent (e.g., automatically generated and sent) from therecipient UE to the sending UE, in accordance with applicable messagerouting rules and logic, and/or other information (e.g.,automatic-response-allowance indicator). In still another aspect, theautomatic response message can be a preconfigured automatic responsemessage or a custom generated automatic response message.

Referring to the drawings, FIG. 1 is a block diagram of an examplesystem 100 that can conditionally forward messages (e.g., text messages(e.g., short message service (SMS), enhanced message service (EMS)),multimedia messages (e.g., multimedia messaging service (MMS)), instantmessages, Session Initiation Protocol (SIP) messages, etc.) inaccordance with various aspects and embodiments of the disclosed subjectmatter. Aspects and embodiments of the subject specification can beemployed in wireless, wired and converged (e.g., wireless and wired)communication networks.

In an aspect, the system 100 can include a desired number of UEs (e.g.,mobile and/or wireless communication device, such as a mobile phone(e.g., 3GPP UMTS phone), personal digital assistant (PDA), landlinephone with mobile messaging functionality, computer, IP television(IPTV), gaming console, STB, multi-media recorder/player, videorecorder/player, audio recorder/player, printer, etc.), such as UE 102,UE 104, and/or UE 106 in the communication network environment, whereinUE 102, UE 104, and/or UE 106 can be connected via a wirelesscommunication connection or wireline communication connection to acommunication network 108, for example. In an embodiment, for example, aUE (e.g., UE 106) also or alternatively can have a wirelinecommunication connection with the communication network 108 and/or canbe a wired or landline communication device (e.g., landline phone),which can have a wireline connection to the communication network 108and have messaging functionality to send or receive messages, such asSMS, MMS, or other types of messages (e.g., other types of mobilemessages), to or from other UEs associated with the communicationnetwork 108.

In an aspect, the UE 102 can be connected (e.g., wirelessly connected)to an AP 110 (e.g., macro AP, femto AP, pico AP, etc.) that can serve aspecified coverage area to facilitate communication by the UE 102 andother UEs (e.g., UE 104, UE 106) in the wireless communication networkenvironment. UE 104 can be connected (e.g., wirelessly connected) to anAP 112 (e.g., macro AP, femto AP, pico AP, etc.) that can serve aspecified coverage area (e.g., a different coverage area than AP 110) tofacilitate communication by the UE 104 and other UEs (e.g., UE 102, UE106) in the wireless communication network environment. UE 106 can beconnected (e.g., wirelessly connected) to an AP 114 (e.g., macro AP,femto AP, pico AP, etc.) that can serve a specified coverage area (e.g.,a different coverage area than APs 110 and 112) to facilitatecommunication by the UE 106 and other UEs (e.g., UE 102, UE 104) in thewireless communication network environment. The APs 110, 112, and 114can serve respective coverage cells (e.g., macrocells, femtocells,picocells, etc.) that can cover respective specified areas, and the APs110, 112, and 114 can service mobile wireless devices, such as UE 102,UE 104, and UE 106, located in the respective areas covered by therespective cells, where such coverage can be achieved via a wirelesslink (e.g., uplink (UL), downlink (DL)). When an attachment attempt issuccessful, the UE 102 can be served by the AP 110, UE 104 can be servedby AP 112, and UE 106 can be served by AP 114, and incoming voice anddata traffic can be paged and routed to the UE 102 through the AP 110,to the UE 104 through the AP 112, to the UE 106 through the AP 114,respectively, and outgoing voice and data traffic from the UE 102, UE104, and/or UE 106 can be paged and routed through the AP 110, AP 112,or AP 114, respectively, to other communication devices (e.g., anotherUE) in the communication network environment. In an aspect, UE 102, UE104, and/or UE 106 can be connected and can communicate wirelessly usingvirtually any desired wireless technology, including, for example,cellular, Wi-Fi, Wi-Max, wireless local area networks (WLAN), etc.

In another aspect, the AP 110, AP 112, and AP 114 can be associated with(e.g., communicatively connected to) the communication network 108(e.g., 2G, 3G, 4G, or xG network, where x can be virtually any desiredinteger or real value) that can facilitate wireless connection with theUEs 102, 104, and 106 connected to the respective AP 110, 112, and 114,and facilitate communication by the UE 102, UE 104, UE 106, and/or otherUEs associated with the communication network 108 with othercommunication devices (e.g., wireless communication devices, wirelinecommunication devices) in the communication network environment. Thecommunication network 108 (e.g., a core network, or network comprising acore network) can facilitate routing voice and data communicationsbetween a communication device(s) (e.g., UE 102, UE 104, UE 106) andother communication devices (e.g., UE, landline phone, computer, emailserver, STB, multimedia server, audio server, video server, news server,financial or stock information server, other communication devices,etc.) associated with the core network 108 in the communication networkenvironment. The communication network 108 also can allocate resourcesto the UEs in the communication network 108, convert or enforceprotocols, establish and enforce Quality of Service (QoS) for the UEs,provide applications or services in the communication network 108,translate signals, and/or perform other desired functions to facilitatesystem interoperability and communication in the communication network108 (e.g., wireless portion of the communication network 108 or wirelineportion of the communication network 108). The communication network 108further can include desired components, such as routers, nodes,switches, interfaces, controllers, etc., that can facilitatecommunication of data between communication devices in the communicationnetwork environment.

In accordance with various aspects and embodiments, the communicationnetwork 108 can comprise a network (NW) message management component 116that can conditionally and/or automatically route messages (e.g., routemessage to an intended target UE and/or forward the message to a desiredforward target UE(s)), in accordance with predefined routing criteriaand corresponding predefined routing rules. In an aspect, one or moreUEs (e.g., UE 102, UE 104, UE 106) associated with the communicationnetwork 108 can include respective handset message managementcomponents, such as handset message management component 118, handsetmessage management component 120, and handset message managementcomponent 122, which can facilitate conditionally and/or automaticallyrouting (e.g., forwarding) of messages on a local (e.g., handset) leveland/or setting desired message routing parameters (e.g., to facilitatesetting desired message routing rules) for the respective UEs on thenetwork level (e.g., setting desired message routing parameters with theNW message management component 116) to facilitate intelligent andconditional routing of messages on a network level.

In an aspect, one or more desired message routing rules can be set inand implemented by the NW message management component 116 and/or ahandset message management component (e.g., 118, 120, 122) to facilitatedesired conditional message routing. The message routing rules can bespecified by UE users, communication service providers, or otherauthorized entities. The message routing rules can relate to, forexample, conditions specified by the UE user sending the message withregard to routing (e.g., automatic forwarding) of a message), conditionsspecified by the target UE user with regard to routing (e.g., automaticforwarding) of a message sent to the target UE user, conditionsspecified by a forward target UE user with regard to routing (e.g.,receiving) of a message being forwarded from (or attempted to beforwarded from) the UE of the target UE user to the UE of the forwardtarget UE user, conditions relating to desired time(s) for forwarding ofmessages (e.g., only automatically forward messages, which wereoriginally sent to the target UE from an originating UE(s), to theforward target UE during a specified time period; from the forwardtarget UE side, only receive forwarded messages during a desired timeperiod), conditions relating to routing of a message based at least inpart on priority of the message (e.g., only automatically forward amessage, which was originally sent to a target UE from an originatingUE, to a forward target UE when the message has a priority level that atleast meets a predefined threshold priority level for forwarding; fromthe forward target UE side, only receive a forwarded message, which wasoriginally sent to a target UE from an originating UE, when the messagehas a priority level that at least meets a predefined threshold prioritylevel for receiving a forwarded message), conditions relating to UEidentifiers (e.g., Mobile Subscriber Integrated Services Digital NetworkNumbers (MSISDNs) or other desired UE identifiers) for which messageforwarding is desired (or undesired) (e.g., only automatically forwardmessages originating from a UE identifier included in a set of specifiedallowed UE identifiers; or automatically forward messages, exceptmessages originating from a UE identifier included in a certain set ofprohibited UE identifiers for which automatic forwarding is undesired;from the forward target UE side, only receive forwarded messagesoriginating from a UE identifier included in a set of allowed UEidentifiers), conditions relating to forwarding of messages based atleast in part on a current operating state (e.g., on state, off state,communication connectivity state, etc.) of a target UE and/or forwardtarget UE (e.g., automatically forward messages, which were originallysent to the target UE from an originating UE(s), to the forward targetUE when the target UE is in an off state), conditions relating to thesize of the message or whether there is an attachment with the message(e.g., only automatically forward messages, which were originally sentto the target UE from an originating UE(s), to the forward target UEwhen the particular message is smaller than a predefined thresholdmessage size for forwarding or, alternatively or additionally, when themessage does not include an attachment; from the forward target UE side,only receive forwarded messages when the message is smaller than apredefined threshold message size for receiving a forwarded message or,alternatively or additionally, when the message does not include anattachment), conditions relating to cost and/or whether the target userand/or forward target user has a subscription service for unlimitedmessaging, has a limited messaging plan or is paying for messages on aper message basis (e.g., only automatically forward up to a predefinednumber of messages per billing period; if the UE user is on a limitedmessaging plan, only allow automatic forwarding of messages until themessaging limit for the billing period is reached; from the forwardtarget UE side, only receive up to a predefined number of forwardedmessages per billing period, or, if the user of the forward target UE ison a limited messaging plan, only allow receiving of forwarded messagesuntil the messaging limit for the billing period is reached; and/or acombination of the aforementioned cost-related conditions for a UE userthat can or may forward messages to other UEs and receive forwardedmessages from other UEs), and/or other desired message forwardingconditions.

As desired, during activation of a UE (e.g., 102), the message routingparameters can be set to a default setting on the network side (e.g., atthe NW message management component 118) and/or the local (e.g.,handset) side (e.g., at the handset message management component 120),or one or more message routing rules can be specified (e.g., by the UEuser) and the message routing parameters can be set in accordance withthe desired message routing rules (as desired, message routingparameters, which have not been modified in accordance with the desiredmessage routing rules, can remain at default settings). The applicablemessage management component (e.g., NW message management component 118or handset message management component of a UE) can be employed tomodify message routing parameters for a UE, as desired, at virtually anydesired time after activation as well.

In accordance with an aspect, respective user profiles can be generatedand stored for respective UE users, wherein a user profile can compriseinformation, such as message routing rules (e.g., message forwardingrules, automatic response rules, etc.), message routing parameters, UEidentifiers, and/or other information. A respective user profile can bestored in a data store associated with the NW message managementcomponent 116 and/or in a data store associated with a respectivehandset message management component (e.g., 118, 120, 122) of arespective UE (e.g., 102, 104, 106) of a respective UE user. When amessage is being sent in the communication network 108, the NW messagemanagement component 116 and/or a handset message managementcomponent(s) (e.g., 118, 120, and/or 122), which is associated with a UEassociated with the message (e.g., originating or sending UE, intendedtarget UE, intended forward target UE), can access the respective userprofile(s) (e.g., handset message management component can access theuser profile of the UE user associated therewith) of the respective UEusers to identify or determine a desired routing of the message, inaccordance with all applicable message routing rules (e.g., applicablemessage routing rules associated with the originating UE 102, target UE104, and/or forward target UE 106), information (e.g.,message-forwarding-allowance indicator) contained in the message,applicable message forwarding logic, and/or other desired factors.

In an aspect, an originating UE 102 (which also can be referred to assource or sending UE) which is sending a message to a target UE 104(which also can be referred to as a recipient UE), can place andimplement desired conditions (e.g., using desired message routing rules)regarding whether the message being sent to the target UE 104 can beforwarded to forward target UE(s) 106 (which also can be referred to asforward recipient UE) specified by the target UE 104. The target UE 104also can place and implement desired conditions (e.g., using desiredmessage routing rules) regarding whether a message received from anoriginating UE 102 is to be forwarded to another UE(s). The forwardtarget UE 106 (or intended forward target UE) also can place andimplement desired conditions (e.g., using desired routing rules)regarding whether a message that is being forwarded (or is attempting tobe forwarded) from the target UE 104 to the forward target UE 106 is tobe forwarded to the forward target UE 106.

As one non-limiting example, an originating UE 102 can desire to send amessage to a target UE 104, where the target user of the target UE 104desires to have messages forwarded to a forward target UE 106 for adesired reason(s) (e.g., forward target UE 106 is the target user'spersonal UE, and the target UE 104 is the target user's work UE, and thetarget user desires to only carry one UE for a desired period of time).The message routing rules for the target UE 104 and the forward targetUE 106 can be set to allow and/or request message forwarding such thatmessages sent to the target UE 104 can be forwarded to the forwardtarget UE 106, wherein the message routing rules can be respectivelystored in the respective user profiles associated with the target UE 104and forward target UE 106. If the originating UE 102 has not placed arestriction (e.g., prohibition) on message forwarding (e.g., a messagerouting rule prohibiting forwarding, wherein amessage-forwarding-allowance indicator can be included in theoriginating message and can be set to a definedmessage-forwarding-prohibited value indicating message forwarding is notallowed) for the message the originating UE 102 is sending to the targetUE 104, when the message is sent from the originating UE 102 to thetarget UE 104, the NW message management component 116 can automaticallydetect and intercept the message, access the user profiles associatedwith the UEs 102, 104 and 106 and/or analyze information (e.g.,message-forwarding-allowance indicator that is set to a definedmessage-forwarding-allowed value indicating the message can beforwarded, message-forwarding-allowance indicator that is set to adefined message-forwarding-prohibited value indicating the message isprohibited from being forwarded per the sender's specification)associated with the message, determine that the message is notprohibited by the originating UE 102 from being forwarded based at leastin part on the parameter value of the message-forwarding-allowanceindicator, determine that the target UE 104 desires the message to beforwarded to the forward target UE 106 based at least in part on theuser profile associated with the target UE 104, determine that theforward target UE 106 is not prohibiting the message from beingforwarded to the forward target UE 106 based at least in part on theuser profile associated with the forward target UE 106, deliver themessage to the target UE 104 (e.g., when desired by the target UE userin accordance with the user profile of the target UE user), and delivera copy of the message to the forward target UE 106, wherein the NWmanagement component 116 can replace the recipient address of themessage to send the message copy to the address (e.g., UE identifier)associated with the forward target UE. In an aspect, the messagedelivered to the forward target UE 106 can indicate the originator ofthe message (e.g., UE identifier associated with the originating UE 102and/or associated UE user) and/or the target UE 104 (e.g., UE identifierassociated with the target UE 104 and/or associated target UE user) thatis forwarding the message to the forward target UE 106, in accordancewith applicable message routing rules and the user profile associatedwith the forward target UE 106.

In an aspect, if the originating UE 102 has placed a restriction onmessage forwarding (e.g., with specific regard to that message (e.g.,per message basis) or in accordance with a message forwardingrestriction contained in the user profile, wherein amessage-forwarding-allowance indicator that is set to a definedmessage-forwarding-prohibited value can be inserted into the originatingmessage to facilitate implementing a message routing rule prohibitingforwarding of the message) for the message the originating UE 102 issending to the target UE 104, if the target UE 104 has not specifiedthat the message is to be forwarded, and/or if the forward target UE 106has placed a restriction on receiving the forwarded message (e.g., amessage routing rule prohibiting forwarding the message to the forwardtarget UE), when the message is sent from the originating UE to thetarget UE, the NW message management component 116 can automaticallydetect and intercept the message, access the user profiles associatedwith the UEs 102, 104 and 106 and/or analyze information (e.g.,message-forwarding-allowance indicator). The NW message managementcomponent 116 also can automatically determine that the message isprohibited by the originating UE 102 from being forwarded (e.g., basedat least in part on the message-forwarding-allowance indicator, if it isset to message-forwarding-prohibited value), determine that the targetUE 104 does not desire the message to be forwarded to the forward targetUE 106 (e.g., based at least in part on the user profile associated withthe target UE 104, if the user profile specifies that message forwardingis not desired or requested), and/or determine that the forward targetUE 106 is prohibiting the message from being forwarded to the forwardtarget UE 106 (e.g., based at least in part on the user profileassociated with the forward target UE 106, if that user profileindicates that the forward target UE 106 does not desire to receive theforwarded message), in accordance with the message routing rules basedat least in part on the information contained in the respective userprofiles and/or information associated with the message. The NW messagecomponent 116 can accordingly automatically determine that the messageis not to be forwarded to the forward target UE 106, and canautomatically deliver a copy of the message to the target UE 104, whichcan be stored in a message box, but not deliver a copy of the message tothe forward target UE 106. In an aspect, in the instance where thetarget UE has not requested to forward the message, the NW messagemanagement component 116 can recognize such condition, and can determinethat the message is not to be forwarded, and thus, does not have tofurther analyze other information, such as the user profiles associatedwith the originating UE 102 or forward target UE 106.

As further example, additionally, or alternatively, the respectivehandset message management components 118, 120, and 122 of therespective UEs 102, 104, and 106 (e.g., originating UE, target UE,forward target UE) can control routing of the message in accordance withapplicable message routing rules (e.g., rules as specified by therespective UE users as contained in the respective user profiles and/oras specified with regard to the message on a per message basis). Anoriginating UE 102 can desire to send a message to a target UE 104,where the target user of the target UE 104 desires to have messagesforwarded to a forward target UE 106 for a desired reason(s), theoriginating UE 102 has not placed a restriction to forwarding themessage, and the forward target UE 106 is set to allow the forwardedmessage to be received by the forward target UE 106, in accordance withthe respective applicable routing rules. When the message is sent fromthe originating UE 102 to the target UE 104, the message managementcomponent 120 of the target UE 104 can receive the message, and canautomatically access the user profile associated with the target UE 104,analyze information associated with the message (e.g.,message-forwarding-allowance indicator included with the messageindicating the message can be forwarded) and the user profile associatedwith the target UE 104, and determine the message is not prohibited bythe originating UE 102 from being forwarded and determine the target UE104 desires the message to be forwarded to the forward target UE 106,store the message in a data store associated with the target UE 104, andgenerate and deliver a copy of the message to the forward target UE 106,wherein the copy of the message can replace the recipient address withthe UE identifier associated with the forward target UE 106. The handsetmessage management component 122 of the forward target UE 106 canautomatically detect the forwarded message, identify that the message isa forwarded message (e.g., based at least in part on a forwardingindicator associated with the message that is set to a value to indicatethat the message is a forwarded message), access the user profileassociated with the forward target UE 106, determine that the forwardtarget UE 106 is not prohibiting the message from being forwarded to theforward target UE 106 based at least in part on the user profileassociated with the forward target UE 106, and present the message tothe forward target UE 106 and/or generate and present an alert signal(e.g., an alert message and/or or visual, audio, or other sensorysignal) to alert the user of the forward target UE 106 of the forwardedmessage. Additionally, or alternatively, if the user of the forwardtarget UE 106 desires to decide whether to accept a forwarded message ona per message basis, the handset message management component 122 canpresent the alert signal to the user, can prompt the user to indicatewhether the user desires to accept the forwarded message, and canpresent the forwarded message or not based at least in part on areceived indication from the user.

In an aspect, the message delivered to the forward target UE 106 canindicate the originator of the message (e.g., identifier associated withoriginating UE 102 and/or associated user) and/or the target UE 104(e.g., identifier associated with the target UE 104 and/or associateduser) that is forwarding the message to the forward target UE 106, inaccordance with applicable message routing rules (e.g., as specified inthe user profile associated with the forward target UE 106). Forinstance, the user of the UE 106 can be provided an option (e.g., in amenu) to request that the forwarded message display the identifier ofthe originating UE 102 and/or identifier associated with the target UE104. In another aspect, the user of the forward target UE 106 can bepresented with and, if desired, can select an option (e.g., in a menu) amessaging box option, wherein, when selected, messages forwarded fromthe target UE 104 can be placed in a messaging box, which can beaccessed by the user of the forward target UE 106 when desired. Thehandset message management component 122 can generate and present analert signal to the user of the UE 106 indicating that a forwardedmessage has been received, identifying the originating UE and/orassociated user, identifying the target UE and/or associated userforwarding the message, identifying the number of forwarded messages,identifying the time(s) of the forwarded message(s), and/or otherpresenting other desired information. In another aspect, the user of UE106 can access the message box and perform desired functions (e.g., cansearch, sort, or execute other desired analytical management features)on the forwarded messages therein to selectively read the forwardedmessages.

If it is desired to place a restriction on automatic message forwarding(e.g., a routing rule prohibiting forwarding) for the message theoriginating UE 102 is sending to the target UE 104, when the message isbeing generated to be sent from the originating UE 102 to the target UE104, in response to a received user command to restrict automaticmessage forwarding (e.g., forwarding restriction command based at leastin part on a previous forwarding restriction setting made by the user,or a per-message or one-time forwarding restriction command specificallyrelating to the message being sent), the handset message managementcomponent 118 of the originator UE (e.g., 102) can insert amessage-forwarding-allowance indicator having a definedmessage-forwarding-prohibited value in the message (e.g., as metadata)to indicate that the message is not allowed to be forwarded (e.g.,automatically forwarded) by the target UE 104 to a forward target UE106. The target UE 104 can receive the message and the handset messagemanagement component 120 can detect and identify themessage-forwarding-allowance indicator restricting forwarding themessage. The handset message management component 120 can determine thatthe message is not to be automatically forwarded based at least in parton the message-forwarding-allowance indicator and applicable messagerouting rules and logic, and the message will not be automaticallyforwarded to a forward target UE 106, even if the target UE 104 is setto automatically forward the received message to the forward target UE106.

If the user of the forward target UE 106 desires to prohibit receivingforwarded messages, that user can input information to the forwardtarget UE 106 (or another communication device that can be used toaccess and modify the user profile associated with the forward target UE106) indicating that forwarded messages are not to be received by and/orpresented on the forward target UE 106, and the handset messagemanagement component 122 can receive that input information and themessage routing parameter(s) can be set to prohibit or restrictreceiving and/or presenting messages on the forward target UE 106. Ifthe forward target UE 106 has placed a restriction on receiving theforwarded message (e.g., a routing rule prohibiting forwarding themessage to the forward target UE 106, wherein the routing rule can bestored in the user profile associated with the forward target UE 106),but the target UE 104 is set to automatically forward a received messageto the forward target UE 106 (and the originating UE 102 has notrestricted forwarding of the message), when the message is sent from theoriginating UE 102 to the target UE 104, the handset message managementcomponent 120 of the target UE 104 can determine that the receivedmessage is to be forwarded to the forward target UE 106, based at leastin part on the user profile associated with the target UE 104, and caninsert a forwarding indicator in a copy of the message (e.g., asmetadata) to indicate that the message is a forwarded message as well asreplace the recipient address with the UE identifier associated with theforward target UE 106, and can send a copy of the message to the forwardtarget UE 106.

However, since the forward target UE 106 is restricting receiving orpresenting forwarded messages, the handset message management component122 of the forward target UE 106 can analyze the message and identifythe message as a forwarded message based at least in part on theforwarding indicator in the message, can determine that forwardedmessages are not to be received by or presented on the forward target UE106 based at least in part on the user profile associated with theforwarding target UE 106 (e.g., comprising the message routingparameter(s) providing that forwarded messages are not to be received orpresented), and can refuse or discard the forwarded message withoutpresenting the forwarded message on the forward target UE. Additionally,or alternatively, if the user of the forward target UE 106 desires todecide whether to accept a forwarded message on a per message basis, thehandset message management component 122 can present a message alertsignal (e.g., forwarded message alert signal) to the user, can promptthe user to indicate whether the user desires to accept the forwardedmessage, and can present the forwarded message or not based at least inpart on a received indication (e.g., indication to accept the forwardedmessage, indication declining to accept the forwarded message) from theforward target UE user. In an aspect, the forwarded message can bepre-screened by the handset message management component 122, whereinthe handset message management component 122 can evaluate informationassociated with the forwarded message, such as the identifier of theoriginating UE 102, the identifier of the target UE 104, and/or theforwarding indicator, to facilitate classifying the forwarded message asa forwarded message and/or who originally sent and/or forwarded themessage, and/or determining whether the applicable message routing rulespermit forwarding the forwarded message to the forward target UE 106.

In accordance with another aspect, when desired, an automatic responsemessage can be automatically generated and sent by a target UE (e.g., orforward target UE) to the originating UE (or the target UE thatforwarded a message) in response to receiving a message from theoriginating UE (or the target UE that forwarded a message). For example,an automatic response message can be generated and sent when the messagerecipient or associated UE is not ready to or is unable to receivemessages or cannot respond to messages. The automatic response featurecan be set by the UE user by selecting the automatic response feature ina menu. The automatic response feature can be implemented at the networklevel by the NW message management component 116 and/or at the handsetlevel by a handset message management component (e.g., 118, 120, 122) ofa UE (e.g., 102, 104, 106). The automatic response message can be apreconfigured automatic response message (e.g., “I′m in a meeting, butwill read and/or respond to your message when I get the chance”, “I amunavailable to read and/or respond to your message right now, but willread and/or respond when I get the chance”, etc.), wherein thepreconfigured automatic response messages can be stored in a data store,and/or the automatic response message can be a custom generatedautomatic response message that can be created and edited by the UE userusing the UE (or another communication device, such as a home computer)and stored in a data store. The UE user can use the UE (or othercommunication device) to modify (e.g., change) an automatic responsemessage, and can edit, update, or delete a custom generated automaticresponse message.

In still another aspect, for a UE receiving a message(s), the automaticresponse message(s) can be automatically sent to any or all UEs thatsend a message to the receiving UE, or to a specified UE(s) (e.g., oneor more UEs associated with one or more UE identifiers that arecontained in a list of UEs to which automatic response messages can besent). In yet another aspect, as desired, there can be differentautomatic response messages that can be sent to different UEs from thereceiving UE, wherein the UE user can provide information indicating theparticular automatic response message to send to a particular UE, andthe NW message management component 116 and/or a handset messagemanagement component (e.g., 118, 120, 122) can control sending a desiredautomatic response message to the desired UE.

In another aspect, the NW message management component 116 or a handsetmessage management component (e.g., 118, 120, 122) can control sendingof a desired message(s) to a desired UE(s) at a future time. Forinstance, the UE user can create a message, and can provide informationregarding the time the UE user desires for the message to be sent andthe UE(s) to which the message is to be sent to the NW messagemanagement component 116 or handset message management component (e.g.,118, 120, 122). The NW message management component 116 or handsetmessage management component (e.g., 118, 120, 122) can store the messageand at the desired future time, can automatically send the message tothe desired UE(s).

In still another aspect, the automatic response feature can be leveragedby a UE (e.g., 102, 104, 106) to automatically send a desired predefinedmessage back to a certain communication device(s) associated with acertain communication device identifier(s) (e.g., MSISDN(s)) uponreceipt of a message from the certain communication device(s). Thisfeature can be useful, for example, to automatically send a responsemessage that is a vote in relation to a television show or other eventwithout having to be available to manually send the message.

In yet another aspect, when a UE (e.g., 104) initiates network-basedmessage forwarding or when the UE initiates handset-based messageforwarding but is powered off, the NW message management component 116can verify whether the messaging mail box option for the UE is selected(e.g., checked). If the messaging mail box option has been selected,when a message is sent to the UE, a copy of the forwarded message can bedelivered to a dedicated messaging box of the UE. This can allow theuser of the UE to search, sort, or execute other analytical managementfunctions to selectively read messages in the dedicated messaging box(e.g., a regular messaging box or email box, or a specially configuredmessage box) at a later time (e.g., when the UE is powered on again).

In an aspect, since there may be some UE users who do not desire toreceive automatic response messages in response to their sent messages(e.g., due to the UE user not having an unlimited messaging plan), theoriginating message sent from the originating UE 102 to the target UE104 can be enhanced to include aper-message-automatic-response-allowance indicator that can indicatewhether the originating UE 102 will accept an automatic response messagein response to the originating message. The originating user associatedwith the originating UE can opt in or opt out regarding whether anautomatic response message is allowed to be delivered to the originatingUE 102 from the target UE 104, wherein the decision to opt in or opt outcan be made on a per message basis or can be applied for all messagessent from the originating UE 102.

The subject specification has a number of advantages over conventionalcommunication systems, methods, and devices. For instance, the subjectspecification, by conditionally forwarding message to a forward UE, whenthe message is sent from a source UE to a target UE, in accordance withpredefined routing criteria, can enable communication service providers(e.g., wireless service providers) to offer differentiated and/orenhanced message forwarding features (e.g., SMS or MMS forwardingfeatures), wherein such benefit can result in improved serviceopportunity, increased revenue generation, and increased customersatisfaction, over conventional systems and methods; can offer improvedcomprehensive integrated network-based and/or handset-based messageforwarding features, wherein such benefit can result in improved productflexibility to meet different customer needs or desires, overconventional systems and methods; can offer improved message forwardingprivacy features, wherein such benefit can enable provision of enhanceddifferentiated services and increased customer satisfaction, overconventional systems and methods; can allow trace back of a forwardedmessage's life cycle, which can result in improved differentiatedservices over conventional systems and methods; can provide an audittrail for service providers to support billing (e.g., can bill by perforwarding message or money subscription), which can result in improvedrevenue generation, over conventional systems and methods; and can allowthe subscriber to have greater control over the destination of a messageby prohibiting the message from being forwarded when the predefinedmessage routing rules so specify, which can result in enhanceddifferentiated services and improved information security forsubscribers, over conventional systems and methods.

FIG. 2 depicts a block diagram of an example system 200 that canconditionally forward messages in accordance with aspects andembodiments of the disclosed subject matter. The system 200 can includea desired number of UEs, including UE 202, UE 204, UE 206, and/or UE208, a desired number of APs, including AP 210, AP 212, and/or AP 214, acommunication network 216. The communication network 216 can include aNW message management component 218, and the UEs (e.g., 202, 204, 206,208) can comprise respective handset message management components, suchas respective handset message management components 220, 222, 224,and/or 226. The UEs (e.g., 202, 204, 206, 208), APs (e.g., 210, 212,214), communication network 216, NW message management component 218,and handset message management components (e.g., 220, 222, 224, 226)each can respectively be the same or similar as, and/or comprise thesame or similar functionality as, respective components (e.g.,respectively named components), such as more fully described herein.

In an aspect, the communication network 216 can include a core network228 (e.g., mobile core network) that can facilitate communications byUEs wirelessly connected to the communication network 216. The UEs 202,204, and 206 can be communicatively connected to the core network 228via the respective APs 210, 212, and 214. The core network 228 canfacilitate wireless communication of voice and data associated withcommunication devices, such as UEs 202, 204, and 206, in thecommunication network 216. The core network 228 can facilitate routingvoice and data communications between UEs and/or other communicationdevices (e.g., phone, computer, email server, multimedia server, audioserver, video server, news server, financial or stock informationserver, other communication devices associated with an IP-based network(e.g., the Internet), etc.) associated with the communication network216. The core network 228 also can allocate resources to the UEs (e.g.,202, 204, 206) in the network 216, convert or enforce protocols,establish and enforce Quality of Service (QoS) for the UEs, provideapplications or services in the network, translate signals, and/orperform other desired functions to facilitate system interoperabilityand communication in the wireless communication network. The corenetwork 228 further can include desired components, such as routers,nodes (e.g., SGSN, GGSN, etc.), switches, interfaces, controllers, etc.,that can facilitate communication of data between communication devicesassociated with the communication network 216.

In yet another aspect, the communication network 216 can include anIP-based network 230 that can facilitate communications by UEs that areconnected to the communication network 216 via a wired line or landlineconnection, or a wireless connection. For instance, the UE 208 can becommunicatively connected to the IP-based network 230 via a wired lineor landline, wherein the UE 208 can communicate with other UEs (e.g.,202, 204, 206) connected to the communication network 216.

In an aspect, a wired communication connection between the UE 208 andthe IP-based network 230 can be a communication connection that cancommunicate voice or data, and/or can be a DSL-type or broadbandconnection facilitated via an Ethernet connection, and/or a wirelesscommunication connection can be facilitated via a connection of the UE208 to an AP (not shown). The UE 208 can transmit messages via a wiredor wireless connection through the IP-based network 230, or othercommunication network (not shown), and/or the core network 228 to otherUEs, or by accessing the user account associated with the UE 208 on theservice provider's web site via a wired or wireless communicationconnection, wherein the web site can allow the UE user to use a UE 208to send messages (e.g., SMS, MMS, etc.) from the originating address oridentifier (e.g., MSISDN) associated with the UE 208 via the IP-basednetwork 230 to other UEs associated with the communication network 216.

In accordance with various aspects, as desired, a message can be sentfrom an originating UE to a target UE, and can be automatically and/orconditionally forwarded to a forward target UE and/or an automaticresponse message can be sent (e.g., automatically sent) in response tothe message, in accordance with one or more predefined message routingrules (e.g., including message routing rules provided in respective userprofiles associated with respective UEs) and/or one or more indicators(e.g., message-forwarding-allowance indicator, forwarding indicator,automatic-response-allowance indicator, etc.), as more fully describedherein. As desired, for respective messages, any one of the UEs 202,204, 206, and 208 can be the originating UE, and other of the UEs can bethe target UE(s) or the forward target UE(s). The NW message managementcomponent 218 and/or respective handset message management components222, 224, 226, and/or 228 of the respective UEs 202, 204, 206, and/or208 can facilitate controlling messaging (e.g., conditional automaticforwarding of messages, conditional sending of automatic responsemessages) associated with the UEs associated with the communicationnetwork 216.

FIG. 3 illustrates a block diagram of an example system 300 andcommunication flow relating to conditional message forwarding inaccordance with various aspects and embodiments of the disclosed subjectmatter. The system 300 can include a desired number of UEs, including UE302, UE 304, UE 306, a desired number of APs, including AP 308, AP 310,and/or AP 312, and a core network 314. The core network 314 can beassociated with a NW message management component 316. The UEs (e.g.,302, 304, 306), APs (e.g., 308, 310, 312), core network 314, and NWmessage management component 316, each can respectively be the same orsimilar as, and/or comprise the same or similar functionality as,respective components (e.g., respectively named components), such asmore fully described herein.

In accordance with various aspects, the core network can comprise adesired number of mobile switching centers (MSCs), including MSC 318,MSC 320, and MSC 322, that can be nodes (e.g., service delivery nodes)that can facilitate routing voice calls and messages (e.g., SMS, MMS,etc.) in the core network 314. The core network 314 also can contain amessage service center 324 (e.g., short message service center (SMSC))that can facilitate routing and delivery of messages between UEsassociated with the core network 314.

In other aspects, the core network 314 can include a signaling transferpoint (STP) 326 that can be associated with the message service center324, and can be a router that can facilitate routing traffic (e.g.,route traffic on the an IP-based network, such as the Internet), addresstranslation, and other desired functions, in the core network 314. Thecore network 314 also can include a home location register (HLR) 328that can be associated with the STP 326 and can comprise a database thatincludes information relating to UE users associated with the corenetwork 314. The HLR 328 can include information relating to SIM cardsand MSISDNs, for example. The core network 314 can contain a visitorlocation register (VLR) 330 that can be associated with the HLR 328 andcan include a database that stores information regarding UEs that areassociated with MSCs with which the VLR 330 is associated. In an aspect,an MSC can send information regarding a new UE located in or associatedwith the core network 314 and a new record can be generated for the newUE and stored in the database in the VLR 330, and the HLR 328 can beupdated with regard to the new UE (e.g., location of the new UE can beidentified).

The following is an example communication flow wherein messageforwarding is not desired by the forward target UE or associated forwardtarget UE user. A target UE user can desire to have messages sent totarget UE 304 forwarded to forward target UE 306, and can use the targetUE 304 to communicate with the NW message management component 316 toset a message routing rule that specifies that messages (e.g., SMS, MMS,etc.) sent to the target UE 304 are to be forwarded to the forwardtarget UE 306. The NW message management component 316 can store themessage routing rule in the user profile associated with the target UEuser, wherein the user profile can be stored in a data store (not shownin FIG. 3; e.g., as shown in FIG. 4) associated with the NW messagemanagement component 316.

In another aspect, the forward target UE user can desire to not receivemessages from the originating UE 302, and can use the forward target UE306 to communicate with the NW message management component 316 torequest to set, and set, a message routing rule that declines orprohibits messages, including forwarded messages, from the originatingUE 302. The NW message management component 316 can store that messagerouting rule declining messages from originating UE 302 in the userprofile associated with the forward target UE user, wherein that userprofile can be stored in the data store associated with the NWmanagement component 316.

When a message is sent from originating UE 302 to target UE 304, themessage can be routed through MSC 318 to message service center 324. TheNW message management component 316 can detect and intercept thatmessage, can access the user profiles associated with the target UE userand forward target UE user to analyze the respective message routingrules therein, and can determine that, while the message routing rule inthe user profile of the target UE user requests that the message beforwarded to the forward target UE 306, the message routing rule in theuser profile of the forward target UE user specifies that messages fromoriginating UE 302 are not desired (e.g., are prohibited, or to bedeclined), and applying these message routing rules and logic, candetermine that the message is not to be forwarded to the forward targetUE 306 and the message is to be delivered to a message box 332associated with the target UE 304. The NW message management component316 can communicate with the message service center 324 to notify themessage service center 324 that the message is to be routed anddelivered to the message box 332 associated with the target UE 304, andthe message service center 324 can deliver the message to the messagebox 332.

The following is an example communication flow wherein messageforwarding is not desired by the originating UE or associatedoriginating UE user. A target UE user can desire to have messages thatare sent to target UE 304 forwarded to forward target UE 306, and canuse the target UE 304 to communicate with the NW message managementcomponent 316 to set a message routing rule that specifies that messages(e.g., SMS, MMS, etc.) sent to the target UE 304 are to be forwarded tothe forward target UE 306. The NW message management component 316 canstore the message routing rule in the user profile associated with thetarget UE user, wherein the user profile can be stored in a data store(not shown in FIG. 3; e.g., as shown in FIG. 4) associated with the NWmessage management component 316.

In another aspect, the originating UE user can desire to not havemessages sent from the originating UE 302 forwarded to another UE (e.g.,forward target UE 306), and to facilitate such forwarding restriction,when sending a message to the target UE 304, the originating UE user canuse the originating UE 302 to add a message-forwarding-allowanceindicator (e.g., a per-message message-forwarding-allowance indicator),which is set to message-forwarding-prohibited value (e.g.,message-forwarding-prohibited value can be NO or 0), to the message, andthe message and associated indicator can be sent.

The message can be routed through MSC 318 to message service center 324.The NW message management component 316 can detect and intercept thatmessage, can analyze the information (e.g., indicator) in the message,and can determine that the message-forwarding-allowance indicator in themessage specifies that this message is not to be forwarded, and applyingthe message routing rules and logic, can determine that the message isnot to be forwarded to the forward target UE 306 and the message is tobe delivered to a message box 332 associated with the target UE 304. TheNW message management component 316 can communicate with the messageservice center 324 to notify the message service center 324 that themessage is to be routed and delivered to the message box 332 associatedwith the target UE 304, and the message service center 324 can deliverthe message to the message box 332.

The following is an example communication flow wherein messageforwarding is desired by the targeting UE user and forwarding is notrestricted by the originating UE 302 or forward target UE 306. In anaspect, the target UE user can use the target UE 304 to communicate withthe NW message management component 316 to request, and set a messagerouting rule for, forwarding of messages to forward target UE 306, andthe message routing rule can be stored in the user profile associatedwith the target UE user, wherein that user profile can be stored in adata store associated with the NW message management component 316. Theforward target UE user does not restrict receiving a message from theoriginating UE 302, and the originating UE user does not restrictforwarding of a message being sent from the originating UE 302 to thetarget UE 304.

When a message is sent from the originating UE 302, the message can bereceived by the MSC 318, wherein the NW message management component 316can detect and intercept the message; can analyze the message and candetermine that there is no indicator (or that themessage-forwarding-allowance indicator is set to allow messageforwarding); can access the user profiles associated with the target UEuser, forward target UE user, and originating UE user to analyze therespective message routing rules therein, and can determine that, themessage routing rule in the user profile of the target UE user requeststhat the message be forwarded to the forward target UE 306, and the userprofiles of the originating UE user and forward target UE user do notinclude any rules prohibiting forwarding of the message; and applyingthe message routing rules and logic, can determine that the message isto be forwarded to the forward target UE 306. The NW message managementcomponent 316 can, for example, in a copy of the message, replace therecipient address (e.g., target UE identifier) with the address of theforward target UE 306 (e.g., forward target UE identifier). The copy ofthe message also can include (e.g., optionally, for example, as desiredby the forward target UE and associated user) information indicatingwhich UE (e.g., target UE 304) was the original recipient, so that theforward target UE user can be informed as to which UE was the originalrecipient. The NW message management component 316 can communicate thecopy of the message to the message service center 324 and can notify themessage service center 324 that the message is to be routed anddelivered to the forward target UE 306, and the message service center324 can deliver the message to the forward target UE 306. If the messagebox option has been selected by the target UE user for the target UE304, the message also can be delivered by the message service center 324to the message box 332 associated with the target UE 304.

In accordance with an embodiment of the disclosed subject matter, one ormore components (e.g., UE, NW message management component, handsetmessage management component, etc.) in the communication networkenvironment can utilize artificial intelligence (AI) techniques ormethods to infer (e.g., reason and draw a conclusion based at least inpart on a set of metrics, arguments, or known outcomes in controlledscenarios) an automated response to perform in response to detecting amessage that is being sent from an originating UE to a target UE;whether a message sent from an originating UE to a target UE is to beforwarded to a forward target UE; whether a message sent from anoriginating UE is to be forwarded to a destination besides or inaddition to a target UE and/or forward target UE; a priority levelassociated with a message; etc. Artificial intelligence techniquestypically can apply advanced mathematical algorithms—e.g., decisiontrees, neural networks, regression analysis, principal componentanalysis (PCA) for feature and pattern extraction, cluster analysis,genetic algorithm, and reinforced learning—to historic and/or currentdata associated with the systems and methods disclosed herein tofacilitate rendering an inference(s) related to the systems and methodsdisclosed herein.

In particular, the one or more components in the communication networkenvironment can employ one of numerous methodologies for learning fromdata and then drawing inferences from the models so constructed, e.g.,Hidden Markov Models (HMMs) and related prototypical dependency models.General probabilistic graphical models, such as Dempster-Shafer networksand Bayesian networks like those created by structure search using aBayesian model score or approximation can also be utilized. In addition,linear classifiers, such as support vector machines (SVMs), non-linearclassifiers like methods referred to as “neural network” methodologies,fuzzy logic methodologies can also be employed. Moreover, game theoreticmodels (e.g., game trees, game matrices, pure and mixed strategies,utility algorithms, Nash equilibria, evolutionary game theory, etc.) andother approaches that perform data fusion, etc., can be exploited inaccordance with implementing various automated aspects described herein.The foregoing techniques or methods can be applied to analysis of thehistoric and/or current data associated with systems and methodsdisclosed herein to facilitate making inferences or determinationsrelated to systems and methods disclosed herein.

In accordance with various aspects and embodiments, the subjectspecification can be utilized in wireless, wired, and converged (e.g.,wireless and wired) communication networks. For example, the disclosedsubject matter can be employed in wireless networks, with such networksincluding, for example, 2G type networks, 3G type networks, 4G typenetworks, LTE, Universal Mobile Telecommunications Systems (UMTS), CodeDivision Multiple Access (CDMA) type systems, Wideband CDMA (WCDMA) typesystems, etc.

FIG. 4 depicts a block diagram of an example NW message managementcomponent 400 in accordance with an embodiment of the disclosed subjectmatter. In an aspect, the NW message management component 400 cancomprise a communicator component 402 that can be employed tocommunicate (e.g., transmit, receive) information, including informationrelating to messages, between the NW message management component 400and other components or devices, such as UEs, routers, switches, etc.,associated with a communication network environment.

In an aspect, the NW message management component 400 can contain amonitor component 404 that can monitor messages being communicatedbetween UEs associated with the communication network. In anotheraspect, the NW message management component 400 can include a detectorcomponent 406 that can sense or detect information relating to a messagebeing sent from an originating UE to a target UE, wherein theinformation can include, for example, an originating UE identifier oraddress associated with the message, a target UE identifier or addressassociated with the message, a forward target UE identifier or addressassociated with the message, a type of message, amessage-forwarding-allowance indicator, a forwarding indicator, apriority level, a time of transmission of the message, metadata, etc.,related thereto. In still another aspect, the NW message managementcomponent 400 also can include an interceptor component 408 that canintercept a message that is sent from an originating UE to a target UE,for example, when forwarding (e.g., automatic forwarding) of the messageis desired by the target UE.

In yet another aspect, the NW message management component 400 cancomprise an evaluator component 410 that can evaluate informationrelating to a message sent from an originating UE to a target UE tofacilitate determining whether the message is to be forwarded (e.g.,automatically forwarded) to a forward target UE(s), whether the forwardtarget UE(s) desires to accept a forwarded message, and/or other actionsto take in relation to the message, wherein the information can include,for example, an originating UE identifier or address associated with themessage; a target UE identifier or address associated with the message;a forward target UE identifier or address associated with the message; atype of message; a message-forwarding-allowance indicator; a forwardingindicator; information contained in user profiles respectivelyassociated with the originating UE, target UE, or forward target UE; apriority level; a time of transmission of the message; metadata; etc.

In an aspect, the NW message management component 400 can comprise anindicator component 412 that can generate or insert a desired indicatorinto a message to facilitate desired routing of a message. For example,the indicator component 412 can generate and insert a forwardingindicator in a forwarded message indicating that the message is aforwarded message (e.g., a message is a forwarded message when a messagefrom an originating UE is being forwarded by a target UE to a forwardtarget UE) to facilitate identification of the forwarded message asbeing a forwarded message by the forward target UE.

The NW message management component 400 also can employ a messagegenerator component 414 that can copy and/or generate a message tofacilitate forwarding a message to a desired forward target UE(s) and/orsending the message to another desired destination (e.g., message box).The message generator component 414 can include, in the message,information relating to the original message and/or additionalinformation (e.g., forwarding indicator, forward target UE identifier,destination identifier (e.g., for message box), etc.).

In still another aspect, the NW message management component 400 caninclude a router component 416 that can route messages communicatedbetween UEs in accordance with applicable routing rules. The applicablemessage routing rules can be rules included in user profiles associatedwith UEs related to a particular message, rules implemented in responseto information received from a UE user(s) (e.g., an indication from auser associated with a forward target UE as to whether to receive aforwarded message), service provider rules, etc.

The NW message management component 400 also can include a prioritycomponent 418 that can identify or determine a priority of a messagebeing sent from an originating UE to a target UE to facilitatedetermining whether to forward the message from the target UE to aforward target UE(s). The priority component 418 can identify a prioritylevel in a message (e.g., based at least in part on a priority levelindicator in the message) or can analyze a message (e.g., analyzemessage content or other related information) to identify or determinethe priority level of the message.

In another aspect, the NW message management component 400 can contain atimer component 420 that can track time relating to UEs to facilitatedetermining routing of messages between UEs. For instance, the timercomponent 420 can track and identify a current time a message is beingsent or an amount of time that has elapsed since a routing rule(s)(e.g., routing rule relating to message routing based at least in parton time) has been implemented, wherein the routing rule(s) can be storedin a user profile. For example, a UE user can select a message routingparameter that provides that messages sent to the user's UE (e.g.,target UE) are to be forwarded to a forward target UE during a specifiedperiod of time (e.g., between 3:00 p.m. and 5:00 p.m.) or for aspecified amount of time (e.g., for the next 2 hours). The evaluatorcomponent 410 can operate in conjunction with the timer component 420 tofacilitate determining whether a message to the target UE is to beforwarded to a forward target UE when a time-based routing rule isimplemented.

In yet another aspect, the NW message management component 400 cancomprise an alert component 422 that can generate and transmit a desiredalert signal to a UE (e.g., forward target UE), for example, to alert aUE user that a message is available to be sent to and received by theUE, or is being sent to and received by the UE. The alert signal can be,for example, an alert message, which can include desired information(e.g., the originating identifier, target identifier, time of themessage, priority of the message, etc.), or can be a visual, audio, orother sensory (e.g., vibration) signal.

In an embodiment, the NW message management component 400 optionally caninclude a list component 424 that can generate, maintain, edit, updateone or more lists (e.g., white list, black list, forwarding-desired listor forwarding-allowed list, forwarding-restricted list, automaticresponse list, etc.) of UE identifiers or other information, wherein aUE user can specify UE identifiers that are to be included in aparticular list. For example, the list component 424 can generate a listthat includes respective UE identifiers associated with respective UEsfor which message forwarding is desirable by a forward target UE or alist that includes respective UE identifiers associated with respectiveUEs for which message forwarding is prohibited by a forward target UE.As another example, the list component 424 can generate a list thatincludes respective UE identifiers associated with respective UEs (e.g.,target UE, forward target UE) for which message forwarding is permittedby an originating UE or a list that includes respective UE identifiersassociated with respective UEs (e.g., target UE, forward target UE) forwhich message forwarding is prohibited by an originating UE. As stillanother example, the list component 424 can generate a list(s) thatincludes respective UE identifiers associated with respective UEs (e.g.,originating UE, target UE) for which an automatic response message isdesired to be sent, wherein a respective list can be associated with arespective automatic response message, or a list that includesrespective UE identifiers associated with respective UEs (e.g.,originating UE, target UE) for which an automatic response message isnot desired to be sent. As yet another example, the list component 424can generate a list(s) that includes respective UE identifiersassociated with respective UEs (e.g., target UE, forward target UE) fromwhich receiving an automatic response message is allowed, or a list thatincludes respective UE identifiers associated with respective UEs (e.g.,target UE, forward target UE) from which receiving an automatic responsemessage is not desired.

In yet another aspect, the NW message management component 400 cancomprise a processor component 426 that can work in conjunction with theother components (e.g., communicator component 402, monitor component404, detector component 406, interceptor component 408, evaluatorcomponent 410, indicator component 412, message generator component 414,router component 416, priority component 418, timer component 420, alertcomponent 422, list component 424, etc.) to facilitate performing thevarious functions of the NW message management component 400. Theprocessor component 426 can employ one or more processors,microprocessors, or controllers that can process data, such asinformation relating to messaging by UEs in the communication network,information relating to operations of the NW message managementcomponent 400, and/or other information, etc., to facilitate operationof the NW message management component 400, as more fully disclosedherein, and control data flow between the NW message managementcomponent 400 and other components (e.g., UE, other components in thecommunication network, etc.) associated with the NW message managementcomponent 400.

The NW message management component 400 also can include a data store428 that can store data structures (e.g., user data, metadata), codestructure(s) (e.g., modules, objects, hashes, classes, procedures) orinstructions, information relating to messaging associated with UEsoperating in the communication network, user profiles associated withrespective UEs or UE users, information relating to operations of the NWmessage management component 400, list information, predefined routingcriteria (and corresponding predefined routing rules), etc., tofacilitate controlling operations associated with the NW messagemanagement component 400. In an aspect, the processor component 426 canbe functionally coupled (e.g., through a memory bus) to the data store428 in order to store and retrieve information desired to operate and/orconfer functionality, at least in part, to the communicator component402, monitor component 404, detector component 406, interceptorcomponent 408, evaluator component 410, indicator component 412, messagegenerator component 414, router component 416, priority component 418,timer component 420, alert component 422, list component 424, and/orsubstantially any other operational aspects of the NW message managementcomponent 400.

FIG. 5 depicts a block diagram of an example handset message managementcomponent 500 in accordance with an embodiment of the disclosed subjectmatter. In an aspect, the handset message management component 500 cancomprise a monitor component 502 that can monitor messages beingcommunicated between UEs associated with the communication network. Inanother aspect, the handset message management component 500 can includea detector component 504 that can sense or detect information relatingto a message being sent from an originating UE to a target UE, whereinthe information can include, for example, an originating UE identifieror address associated with the message, a target UE identifier oraddress associated with the message, a forward target UE identifier oraddress associated with the message, a type of message, amessage-forwarding-allowance indicator, a forwarding indicator, apriority level, a time of transmission of the message, metadata, etc.,related thereto. In still another aspect, the handset message managementcomponent 500 also can include a local interceptor component 506 thatcan intercept a message that is sent from an originating UE to a targetUE that includes the handset message management component 500, forexample, when forwarding (e.g., automatic forwarding) of the message isdesired by the target UE and allowed by the originating UE that sent themessage to the target UE.

In yet another aspect, the handset message management component 500 cancomprise an evaluator component 508 that can evaluate informationrelating to a message sent from an originating UE to a target UE tofacilitate determining whether the message is to be forwarded (e.g.,automatically forwarded) to a forward target UE(s), whether the forwardtarget UE(s) desires to accept a forwarded message, and/or other actionsto take in relation to the message, wherein the information can include,for example, an originating UE identifier or address associated with themessage; a target UE identifier or address associated with the message;a forward target UE identifier or address associated with the message; atype of message; a message-forwarding-allowance indicator; a forwardingindicator; information contained in user profiles respectivelyassociated with the originating UE, target UE, or forward target UE; apriority level; a time of transmission of the message; metadata; etc.

In an aspect, the handset message management component 500 can comprisean indicator component 510 that can generate or insert a desiredindicator into a message to facilitate desired routing of a message. Forexample, the indicator component 510 can generate and insert aforwarding indicator in a forwarded message indicating that the messageis a forwarded message (e.g., a message is a forwarded message when amessage from an originating UE is being forwarded by a target UE to aforward target UE) to facilitate identification of the forwarded messageas being a forwarded message by the forward target UE. As anotherexample, the indicator component 510 can generate and insert amessage-forwarding-allowance indicator in a message (e.g., originatingmessage) that can indicate whether forwarding of the message ispermitted or prohibited.

The handset message management component 500 also can employ a messagegenerator component 512 that can copy and/or generate a message tofacilitate forwarding a message to a desired forward target UE(s) and/orsending the message to another desired destination (e.g., message box).The message generator component 512 can include, in the message,information relating to the original message and/or additionalinformation (e.g., forwarding indicator, forward target UE identifier,destination identifier (e.g., for message box), etc.).

In still another aspect, the handset message management component 500can include a router component 514 that can route messages communicatedbetween UEs in accordance with applicable routing rules. The applicablemessage routing rules can be rules included in user profiles associatedwith UEs that are related to a particular message, rules implemented inresponse to information received from a UE user(s) (e.g., an indicationfrom a user associated with a forward target UE as to whether to receivea forwarded message), rules created by a service provider(s), etc.

The handset message management component 500 also can include a prioritycomponent 516 that can identify or determine a priority of a messagebeing sent from an originating UE to a target UE to facilitatedetermining whether to forward the message from the target UE to aforward target UE(s). The priority component 516 can identify a prioritylevel in a message (e.g., based at least in part on a priority levelindicator in the message) or can analyze a message (e.g., analyzemessage content or other related information) to identify or determinethe priority level of the message.

In another aspect, the handset message management component 500 cancontain a timer component 518 that can track time relating to UEs tofacilitate determining routing of messages between UEs. For instance,the timer component 518 can track and identify a current time a messageis being sent or an amount of time that has elapsed since a routingrule(s) (e.g., routing rule relating to message routing based at leastin part on time) has been implemented, wherein the routing rule(s) canbe stored in a user profile. For example, a UE user can select a messagerouting parameter that provides that messages sent to the user's UE(e.g., target UE) are to be forwarded to a forward target UE during aspecified period of time (e.g., between 3:00 p.m. and 5:00 p.m.) or fora specified amount of time (e.g., for the next 2 hours). The evaluatorcomponent 508 can operate in conjunction with the timer component 518 tofacilitate determining whether a message to the target UE is to beforwarded to a forward target UE when a time-based routing rule isimplemented.

In yet another aspect, the handset message management component 500 cancomprise an alert component 520 that can generate and present a desiredalert signal on the associated UE, for example, to alert the UE userthat a message (e.g., forwarded message) is available to be received bythe UE or is being received by the UE. The alert signal can be, forexample, an alert message, which can include desired information (e.g.,the originating identifier, target identifier, time of the message,priority of the message, etc.), or can be a visual, audio, or othersensory (e.g., vibration) signal.

In an embodiment, the handset message management component 500optionally can include a list component 522 that can generate, maintain,edit, update one or more lists (e.g., white list, black list,forwarding-desired list or forwarding-allowed list,forwarding-restricted list, automatic response list, etc.) of UEidentifiers or other information, wherein a UE user can specify UEidentifiers that are to be included in a particular list. The listcomponent 522 can comprise the same or similar functionality as listcomponent 424, for example.

In yet another aspect, the handset message management component 500 cancomprise a processor component 524 that can work in conjunction with theother components (e.g., monitor component 502, detector component 504,interceptor component 506, evaluator component 508, indicator component510, message generator component 512, router component 514, prioritycomponent 516, timer component 518, alert component 520, list component522, etc.) to facilitate performing the various functions of the handsetmessage management component 500. The processor component 524 can employone or more processors, microprocessors, or controllers that can processdata, such as information relating to messaging by UEs in thecommunication network, information relating to operations of the handsetmessage management component 500, and/or other information, etc., tofacilitate operation of the handset message management component 500, asmore fully disclosed herein, and control data flow between the handsetmessage management component 500 and other components (e.g., UEs, APs,other components in the communication network, etc.) associated with thehandset message management component 500.

The handset message management component 500 also can include a datastore 526 that can store data structures (e.g., user data, metadata),code structure(s) (e.g., modules, objects, hashes, classes, procedures)or instructions, information relating to messaging associated with UEsoperating in the communication network, user profiles associated withrespective UEs or UE users, information relating to operations of thehandset message management component 500, list information, predefinedrouting criteria (and corresponding predefined routing rules), etc., tofacilitate controlling operations associated with the handset messagemanagement component 500. In an aspect, the processor component 524 canbe functionally coupled (e.g., through a memory bus) to the data store526 in order to store and retrieve information desired to operate and/orconfer functionality, at least in part, to the monitor component 502,detector component 504, interceptor component 506, evaluator component508, indicator component 510, message generator component 512, routercomponent 514, priority component 516, timer component 518, alertcomponent 520, list component 522, and/or substantially any otheroperational aspects of the handset message management component 500.

FIG. 6 depicts a block diagram of an example UE 600 in accordance withan aspect of the disclosed subject matter. In an aspect, the UE 600 canbe a multimode access terminal, wherein a set of antennas 669 ₁-669 _(Q)(Q is a positive integer) can receive and transmit signal(s) from and towireless devices like access points, access terminals, wireless portsand routers, and so forth, that operate in a radio access network. Itshould be appreciated that antennas 669 ₁-669 _(Q) are a part ofcommunication platform 602, which comprises electronic components andassociated circuitry that provide for processing and manipulation ofreceived signal(s) and signal(s) to be transmitted; e.g., receivers andtransmitters 604, multiplexer/demultiplexer (mux/demux) component 606,and modulation/demodulation (mod/demod) component 608.

In another aspect, the UE 600 can include a multimode operationchipset(s) 610 that can allow the UE 600 to operate in multiplecommunication modes in accordance with disparate technical specificationfor wireless technologies. In an aspect, multimode operation chipset(s)610 can utilize communication platform 602 in accordance with a specificmode of operation (e.g., voice, GPS). In another aspect, multimodeoperation chipset(s) 610 can be scheduled to operate concurrently (e.g.,when Q>1) in various modes or within a multitask paradigm.

In still another aspect, the UE 600 can comprise a handset messagemanagement component 612 that can facilitate conditionally controllingforwarding (e.g., automatic forwarding) of messages being sent to the UE600, sent from the UE 600, and/or forwarded on behalf of the UE 600, asmore fully described herein. The handset message management component612 also can facilitate conditionally controlling generating, sending,and/or receiving of automatic response messages and/or selecting andcontrolling other messaging options, as more fully described herein. Thehandset message management component 612 also can interact orcommunicate with a NW message management component to facilitate settingdesired message routing rules, desired message routing parameters,messaging options, and/or other desired parameters to facilitateconditionally controlling forwarding of messages, or generating, sendingor receiving automatic response messages, on a network level.

The UE 600 can contain an interface component 614 that can comprise oneor more interfaces (e.g., display screens, touch screens, buttons,controls, switches, adapters, connectors, speakers, etc.) that can beutilized to facilitate presentation of information to a UE user orreceiving data input from a UE user. In an aspect, the interfacecomponent 614 can present messages or information related to messages tothe UE user. For example, the interface component 614 can operate inconjunction with the handset message management component 612 tofacilitate presentation of buttons, controls, or menus to facilitateselecting or setting desired message routing rules, message routingparameters, messaging options, etc. In an aspect, the interfacecomponent 614 can receive input, via manipulation of buttons, controls,or menus by the UE user to facilitate selecting or setting desiredmessage routing rules, message routing parameters, messaging options,etc, and the UE 600 can be configured to operate in accordance with thesuch received input and/or information relating to such received inputcan be communicated to a NW message management component or otherdesired component in the communication network. In an embodiment, if amessage (e.g., forwarded message) is locally blocked from being receivedby the UE 600, for example, when the message routing rules of the UE 600are set to prohibit receiving forwarded messages or when a UE user(e.g., forward target UE user) declines to accept a forwarded message,the interface component 614 can facilitate automatic or manualtransmission of a signal or message from the UE 600 to a NW messagemanagement component in the communication network to convey to the NWmessage management component that the message (e.g., forwarded message)was locally declined by the UE 600, and the user account associated withthe UE 600 can or may be credited (or not billed) for costs related tothe undelivered message.

In still another aspect, the UE 600 also can include a processor(s) 616that can be configured to confer functionality, at least in part, tosubstantially any electronic component within the UE 600, in accordancewith aspects of the disclosed subject matter. For example, theprocessor(s) 616 can facilitate enabling the UE 600 to process data(e.g., symbols, bits, or chips) for multiplexing/demultiplexing,modulation/demodulation, such as implementing direct and inverse fastFourier transforms, selection of modulation rates, selection of datapacket formats, inter-packet times, etc. As another example, theprocessor(s) 616 can facilitate enabling the UE 600 to process datarelating to messaging, voice calls, or other services (e.g., Internetservices or access, services related to applications, etc.).

The UE 600 also can contain a data store 618 that can store datastructures (e.g., user data, metadata); code structure(s) (e.g.,modules, objects, classes, procedures) or instructions; message hashes;neighbor cell list; one or more lists (e.g., whitelist; blacklist,forwarding-desired list or forwarding-allowed list,forwarding-restricted list, automatic response list, etc.); informationrelating to messaging (e.g., message routing rules, message-relatedindicators, message routing parameters, messaging options, etc.), voicecalls, or other services associated with the UE 600; network or deviceinformation like policies and specifications; attachment protocols; codesequences for scrambling, spreading and pilot (e.g., referencesignal(s)) transmission; frequency offsets; cell IDs; encodingalgorithms; compression algorithms; decoding algorithms; decompressionalgorithms; and so on. In an aspect, the processor(s) 616 can befunctionally coupled (e.g., through a memory bus) to the data store 618in order to store and retrieve information (e.g., neighbor cell list;information relating to mobile messaging, voice calls, or otherservices; frequency offsets; desired algorithms; etc.) desired tooperate and/or confer functionality, at least in part, to communicationplatform 602, multimode operation chipset(s) 610, handset messagemanagement component 612, and interface component 614, and/orsubstantially any other operational aspects of the UE 600.

FIG. 7 illustrates a block diagram of an example AP 700 (e.g.,femtocell, picocell, macro base station, etc.) in accordance with anaspect of the disclosed subject matter. The AP 700 can receive andtransmit signal(s) from and to wireless devices like access points(e.g., femtocells, picocells, base stations, etc.), access terminals(e.g., UEs), wireless ports and routers, and the like, through a set ofantennas 769 ₁-769 _(N). In an aspect, the antennas 769 ₁-769 _(N) are apart of a communication platform 702, which comprises electroniccomponents and associated circuitry that can provide for processing andmanipulation of received signal(s) and signal(s) to be transmitted. Inan aspect, the communication platform 702 can include areceiver/transmitter 704 that can convert signal from analog to digitalupon reception, and from digital to analog upon transmission. Inaddition, receiver/transmitter 704 can divide a single data stream intomultiple, parallel data streams, or perform the reciprocal operation.

In an aspect, coupled to receiver/transmitter 704 can be amultiplexer/demultiplexer (mux/demux) 706 that can facilitatemanipulation of signal in time and frequency space. The mux/demux 706can multiplex information (e.g., data/traffic and control/signaling)according to various multiplexing schemes such as, for example, timedivision multiplexing (TDM), frequency division multiplexing (FDM),orthogonal frequency division multiplexing (OFDM), code divisionmultiplexing (CDM), space division multiplexing (SDM), etc. In addition,mux/demux component 706 can scramble and spread information (e.g.,codes) according to substantially any code known in the art, e.g.,Hadamard-Walsh codes, Baker codes, Kasami codes, polyphase codes, and soon. A modulator/demodulator (mod/demod) 708 also can be part of thecommunication platform 702, and can modulate information according tomultiple modulation techniques, such as frequency modulation, amplitudemodulation (e.g., M-ary quadrature amplitude modulation (QAM), with M apositive integer), phase-shift keying (PSK), and the like.

The AP 700 also can comprise a processor(s) 710 that can be configuredto confer and/or facilitate providing functionality, at least partially,to substantially any electronic component in or associated with the AP700. For instance, the processor(s) 710 can facilitate operations ondata (e.g., symbols, bits, or chips) for multiplexing/demultiplexing,modulation/demodulation, such as effecting direct and inverse fastFourier transforms, selection of modulation rates, selection of datapacket formats, inter-packet times, etc. The processor(s) 710 also canfacilitate other operations on data, for example, to facilitate managingor maintaining a white list that includes information, such ascommunication device identifiers associated with communication devicesthat can connect to the AP 700 to communicate voice or data, etc.

In another aspect, the AP 700 can include a data store 712 that canstore data structures; code instructions; rate coding information;information relating to measurement of radio link quality or receptionof information related thereto; information relating to establishing acommunications connection between a communication device (e.g., UE) andother communication devices, white list information, informationrelating to managing or maintaining the white list; system or deviceinformation like policies and specifications; code sequences forscrambling; spreading and pilot transmission; floor plan configuration;access point deployment and frequency plans; scheduling policies; and soon. The processor(s) 710 can be coupled to the data store 712 in orderto store and retrieve information (e.g., information, such asalgorithms, relating to multiplexing/demultiplexing ormodulation/demodulation, information relating to radio link levels,information relating to establishing communication connectionsassociated with a UE(s) served by the AP 700, information relating tothe white list, etc.) desired to operate and/or confer functionality tothe communication platform 702, and/or other operational components ofAP 700.

In view of the example systems and/or devices described herein, examplemethodologies that can be implemented in accordance with the disclosedsubject matter can be better appreciated with reference to flowcharts inFIGS. 8-11. For purposes of simplicity of explanation, examplemethodologies disclosed herein are presented and described as a seriesof acts; however, it is to be understood and appreciated that theclaimed subject matter is not limited by the order of acts, as some actsmay occur in different orders and/or concurrently with other acts fromthat shown and described herein. For example, a method disclosed hereincould alternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methodologies in accordance with the disclosed subject matterwhen disparate entities enact disparate portions of the methodologies.Furthermore, not all illustrated acts may be required to implement amethod in accordance with the subject specification. It should befurther appreciated that the methodologies disclosed throughout thesubject specification are capable of being stored on an article ofmanufacture to facilitate transporting and transferring suchmethodologies to computers for execution by a processor or for storagein a memory.

FIG. 8 presents a flowchart of an example method 800 for conditionalforwarding of messages in accordance with various aspects andembodiments of the disclosed subject matter. At 802, a message sent froman originating UE to a target UE can be intercepted.

At 804, a determination can be made regarding whether to forward a copyof the message to a forward target UE based at least in part on one ormore predefined message routing rules. In an aspect, a messagemanagement component (e.g., NW message management component, handsetmanagement component) can analyze information associated with themessage (e.g., UE identifiers, associated indicators, etc.) and/or userprofiles associated with the originating UE, target UE, and/or forwardtarget UE, wherein applicable message routing rules can be identified,to facilitate determining whether to send a copy of the message to aforward target UE or not. If in accordance with the applicable messagerouting rules, a copy of the message is to be forwarded to the forwardtarget UE, a copy of the message can be forwarded to the forward targetUE, wherein the recipient address in the message copy can be replacedwith the UE identifier associated with the forward target ID tofacilitate delivering the message copy to the forward target UE. If inaccordance with the applicable message routing rules, a copy of themessage is not to be forwarded to the forward target UE, no copy of themessage will be forwarded to the forward target UE, although, asdesired, the message can be delivered to the target UE and/or a messagebox (e.g., electronic message box) associated with the target UE.

FIG. 9 illustrates a flowchart of an example method 900 that canconditionally forward messages in accordance with various aspects of thedisclosed subject matter. At 902, communications (e.g., messages)associated with a communication network can be monitored. At 904, amessage can be detected. At 906, information relating to the message canbe evaluated. The information can comprise message content, metadata(e.g., priority level, size, time message was sent, indicator (e.g.,message-forwarding-allowance indicator)), originating UE identifiertarget UE identifier, user profiles (e.g., user profile associated withoriginating UE, user profile associated with target UE, user profileassociated with forward target UE), applicable message routing rules(e.g., as contained in the user profiles, etc.

At 908, a determination can be made regarding whether the target UE orassociated target UE user desires (e.g., requests) that the message beforwarded to a forward target UE. For instance, information contained inthe user profile associated with the target UE or target UE user can beanalyzed to determine whether the target UE or associated target UE userdesires to have the message forwarded to a forward target UE. Forexample, the user profile can comprise information providing thatmessages from that originating UE are to be forwarded to the desiredforward target UE, messages sent to the target UE during a specifiedtime period are to be forwarded to the forward target UE, or messageshaving at least a predefined minimum threshold priority level forforwarding are to be forwarded to the forward target UE, among othermessage routing criteria and message routing rules, such as more fullydisclosed herein, that can be employed.

If it is determined that there is no desire to forward the message(e.g., the target UE has not requested to automatically forward themessage), at 910, a copy of the message will not be forwarded to aforward target UE, although the message can be delivered to the targetUE and/or optionally a copy of the message can be delivered to a messagebox associated with the target UE. If, at 908, it is determinedforwarding of the message is desired (e.g., by the target UE orassociated target UE user), at 912, a determination can be maderegarding whether the originating UE or associated originating UE useris prohibiting forwarding of the message. For instance, amessage-forwarding-allowance indicator associated with the message canbe evaluated to identify whether forwarding of the message has beenprohibited by the originating UE (or associated user).

If it is determined that forwarding of the message is prohibited by theoriginating UE (or associated originating UE user), at 914, a copy ofthe message will not be forwarded to the forward target UE, although themessage can be delivered to the target UE and/or optionally a copy ofthe message can be delivered to a message box associated with the targetUE. For example, if message-forwarding-allowance indicator is set to amessage-forwarding-prohibited value, it can be determined thatforwarding of the message is prohibited by the originating UE (ororiginating UE user). The message-forwarding-allowance indicator can beattached to or inserted in the message on a per message basis or inaccordance with information contained in the user profile associatedwith the originating UE or originating UE user. Alternatively, if thereis no message-forwarding-allowance indicator in the message, this canindicate that forwarding of the message is not restricted, and includinga message-forwarding-allowance indicator in the message can indicatethat forwarding of the message is restricted.

If, at 912, it is determined that forwarding of the message is notprohibited by the originating UE (or associated originating UE user)(e.g., message-forwarding-allowance indicator is set tomessage-forwarding-allowed value), at 916, a determination can be maderegarding whether forwarding of the message to the forward target UE isprohibited by the forward target UE or associated forward target UEuser. For instance, information in the user profile associated with theforward target UE can be analyzed to determine whether the forwardtarget UE prohibits forwarding of message to the forward target UEand/or an alert (e.g., forwarding message alert) can be sent to theforward target UE to prompt the forward target UE user to indicatewhether the forward target UE user desires to receive the forwardedmessage or not. In an aspect, when conditional message forwardingcontrol is being performed on a local level by the handset messagemanagement component associated with the forward target UE, the handsetmessage management component can recognize or identify that the messageis a forwarded message based at least in part on a forwarding indicatorthat can be included in or associated with the copy of the message beingforwarded.

If it is determined that forwarding of the message to the forward targetUE is prohibited by the forward target UE or associated forward targetUE user, at 918, a copy of the message will not be forwarded to theforward target UE, although the message can be delivered to the targetUE and/or optionally a copy of the message can be delivered to a messagebox associated with the target UE and/or to a message box associatedwith the forward target UE. For instance, information (e.g., messagerouting rule(s)) contained in the user profile associated with theforward target UE or associated forward target UE user, or informationreceived from the forward target UE user, can be analyzed to determinewhether forwarding of the message to the forward target UE is prohibitedby the forward target UE or associated forward target UE user. If amessage routing rule(s) or information received from the forward targetUE user indicates that message forwarding is prohibited, the messagewill not be forwarded to the forward target UE.

If, at 916, it is determined that forwarding of the message to theforward target UE is not prohibited by the forward target UE orassociated forward target UE user, at 920, a copy of the message can beforwarded to the forward target UE, wherein the recipient address in thecopy of the message being forwarded can be replaced with the UEidentifier associated with the forward target UE (e.g., by the NWmessage management component or by the handset message managementcomponent associated with the target UE) to facilitate delivery of themessage copy to the forward target UE. Also, the message can bedelivered to the target UE and/or optionally a copy of the message canbe delivered to a message box associated with the target UE and/or to amessage box associated with the forward target UE.

FIG. 10 depicts a flowchart of an example method 1000 that can employone or more message routing rules or messaging options to facilitateconditional forwarding of messages in accordance with aspects of thedisclosed subject matter. At 1002, information relating to a messagerouting rule(s) or messaging option(s) can be received. For instance,information can be received from a UE user, wherein the information canrelate to message routing rules or messaging options that are desired tobe implemented in relation to conditional forwarding of messages betweenUEs. The message routing rules or messaging options can relate toconditions on message forwarding when the UE user (or associated UE) isthe originating UE user (e.g., message sender) (or associatedoriginating UE), the target UE user (e.g., message recipient) (orassociated target UE), or the forward target UE user (e.g., recipient ofthe forwarded message) (or associated forward target UE), whether anautomatic response message is to be automatically sent to the UE fromwhich a message (e.g., forwarded message) was received or originallysent, whether a copy of the message is to be delivered to a message box,etc. The message routing rules can relate to, for example, conditionalmessage forwarding (e.g., message forwarding based at least in part onwhether the message sender prohibits forwarding of the message, whetherthe target UE user desires to forward the message, whether the forwardtarget UE user desires to receive a forwarded message, current operatingstate of the target UE and/or forward target UE, priority level of themessage, time of transmission of the message, cost of forwarding amessage, whether the message includes an attachment, size of themessage, or other desired factors) or conditional sending of automaticresponse messages, such as more fully disclosed herein. The messagingoptions can relate to, for example, whether a target UE user or forwardtarget UE user desire to have a copy of a message (e.g., message from anoriginating UE, forwarded message from a target UE) delivered to arespective message box.

At 1004, the information, or a desired portion thereof, relating to themessage routing rules or messaging options can be stored, for example,in the user profile associated with the UE user or associated UE. Theinformation also can include message routing parameters or messagingoption parameters that correspond to the received information, forexample.

At 1006, at least one message can be routed based at least in part oninformation stored in the user profile. When a message is intercepted tofacilitate determining whether the message is to be forwarded or not,and the message relates to the user profile (e.g., the user profile isassociated with the originating UE (or originating UE user), target UE(or associated target UE user), or forward target UE (or associatedforward target UE user)), the user profile can be accessed andinformation stored therein can be analyzed to facilitate determiningwhether the message is to be forwarded or not. The message can beforwarded or not based at least in part on the user profile, otherrelated profiles associated with other UEs related to the message,received information (e.g., per message message-forwarding-allowanceindicator, received information forward target UE indicating thatforwarding of the message is not desired, etc.), and/or other messagerouting criteria or rules or other information.

FIG. 11 illustrates a flowchart of an example method 1100 that canconditionally send an automatic response message in response to areceived message in accordance with aspects of the disclosed subjectmatter. At 1102, a message can be received by a receiving UE from asending UE. The message can be one that is received from an originatingUE by a target UE or received from a target UE by a forward target UE.

At 1104, a determination can be made regarding whether the receiving UEdesires to send (e.g., automatically send) an automatic response messageto the sending UE. For instance, the user profile associated with thereceiving UE (e.g., a target UE receiving a message from an originatingUE, a forward target UE receiving a forwarded message from a target UE)can be analyzed, and based at least in part on analysis of theinformation contained in the user profile, it can be determined whetherthe receiving UE (or associated UE user) desires to send an automaticresponse message to the sending UE. If it is determined that thereceiving UE (or associated UE user) does not desire to send anautomatic response message to the sending UE, at 1106, no automaticresponse message is sent by the receiving UE to the sending UE.

If, at 1104, it is determined that the receiving UE (or associated UEuser) desires to send an automatic response message to the sending UE,at 1108, a determination can be made regarding whether the sending UEdoes not desire to receive (e.g., prohibits receiving) an automaticresponse message. The determination regarding whether the sending UEdoes not desire to receive an automatic response message can be madebased at least in part on an automatic-response-allowance indicatorassociated with the message sent to the receiving UE. For example, anautomatic-response-allowance indicator can be associated with (e.g.,attached to or included in) the message, wherein theautomatic-response-allowance indicator can be set to anautomatic-response-allowed value to indicate that the sending UE doesnot prohibit receiving an automatic response message from the receivingUE or set to an automatic-response-prohibited value to indicate that thesending UE does not desire (e.g., prohibits) receiving an automaticresponse message from the receiving UE.

If it is determined that the sending UE does not desire to receive anautomatic response message in response to sending the message to thereceiving UE, at 1110, no automatic response message is sent to thesending UE from the receiving UE. If, at 1108, it is determined that thesending UE does not prohibit receiving an automatic response message inresponse to sending the message to the receiving UE, at 1112, anautomatic response message can be sent to the sending UE from thereceiving UE. The automatic response message can be a preconfiguredmessage (e.g., “I am unavailable to view your message at this time, butwill view and/or respond to your message as soon as I can”) desired bythe receiving UE (e.g., the automatic response message sender).

It is to be appreciated and understood that components (e.g., UE, AP,communication network, NW message management component, handset messagemanagement component, etc.), as described with regard to a particularsystem or method, can include the same or similar functionality asrespective components (e.g., respectively named components or similarlynamed components) as described with regard to other systems ormethodologies disclosed herein.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “data store,” data storage,”“database,” and substantially any other information storage componentrelevant to operation and functionality of a component, refer to “memorycomponents,” or entities embodied in a “memory” or components comprisingthe memory. For example, information relevant to operation of variouscomponents described in the disclosed subject matter, and that can bestored in a memory, can comprise, but is not limited to comprising,subscriber information; cell configuration (e.g., devices served by anAP) or service policies and specifications; privacy policies; and soforth. It will be appreciated that the memory components describedherein can be either volatile memory or nonvolatile memory, or caninclude both volatile and nonvolatile memory. By way of illustration,and not limitation, nonvolatile memory can include read only memory(ROM), programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable ROM (EEPROM), phase change memory (PCM), flashmemory, or nonvolatile RAM (e.g., ferroelectric RAM (FeRAM). Volatilememory can include random access memory (RAM), which acts as externalcache memory. By way of illustration and not limitation, RAM isavailable in many forms such as synchronous RAM (SRAM), dynamic RAM(DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM),enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM(DRRAM). Additionally, the disclosed memory components of systems ormethods herein are intended to comprise, without being limited tocomprising, these and any other suitable types of memory.

Various aspects or features described herein may be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips . . . ), opticaldisks (e.g., compact disk (CD), digital versatile disk (DVD), Blu-raydisc (BD), . . . ), smart cards, and flash memory devices (e.g., card,stick, key drive . . . ).

What has been described above includes examples of systems and methodsthat provide advantages of the disclosed subject matter. It is, ofcourse, not possible to describe every conceivable combination ofcomponents or methodologies for purposes of describing the claimedsubject matter, but one of ordinary skill in the art may recognize thatmany further combinations and permutations of the claimed subject matterare possible. Furthermore, to the extent that the terms “includes,”“has,” “possesses,” and the like are used in the detailed description,claims, appendices and drawings such terms are intended to be inclusivein a manner similar to the term “comprising” as “comprising” isinterpreted when employed as a transitional word in a claim.

1. A system, comprising: a communication network that is configured tofacilitate communication of at least one message from an originatingcommunication device to at least a target communication deviceassociated with the communication network; and at least one messagemanagement component that is configured to route the at least onemessage to the target communication device and determine whether toforward a copy of the at least one message to a forward targetcommunication device, based at least in part on one or more predefinedmessage routing rules.
 2. The system of claim 1, wherein the at leastone message management component comprises at least one of a networkmessage management component associated with the communication networkor at least one handset message management component associated with atleast one of the originating communication device, the targetcommunication device, or the forward target communication device.
 3. Thesystem of claim 1, wherein the at least one message management componentis further configured to analyze a user profile associated with thetarget communication device to facilitate determination of whetherforwarding of the at least one message is requested in relation to thetarget communication device.
 4. The system of claim 3, wherein the atleast one message management component is further configured tointercept the at least one message when it is determined that forwardingof the at least one message is requested in relation to the targetcommunication device.
 5. The system of claim 3, wherein the at least onemessage management component is further configured to analyze amessage-forwarding-allowance indicator associated with the at least onemessage to facilitate determination of whether forwarding of the atleast one message is prohibited by the originating communication device.6. The system of claim 3, wherein the at least one message managementcomponent is further configured to analyze at least one of a forwardingindicator associated with the copy of the at least one message, a userprofile associated with the forward target communication device, orinformation received via the forward target communication device, tofacilitate determination of whether forwarding of the at least onemessage is prohibited by the forward target communication device.
 7. Thesystem of claim 1, wherein the at least one message management componentis further configured to analyze information relating to at least one ofthe at least one message or the copy of the at least one message tofacilitate determination of whether an automatic response message is tobe sent to at least one of the originating communication device or thetarget communication device.
 8. The system of claim 7, wherein the atleast one message management component is further configured todetermine that the automatic response message is to be sent to the atleast one of the originating communication device or the targetcommunication device when the information relating to at least one ofthe at least one message or the copy of the at least one messageincludes an automatic-response-allowance indicator that indicates thatthe automatic response message is not prohibited.
 9. The system of claim7, wherein the at least one message management component is furtherconfigured to determine that the automatic response message is not to besent to the at least one of the originating communication device or thetarget communication device when the information relating to at leastone of the at least one message or the copy of the at least one messageincludes an automatic-response-allowance indicator that indicates thatthe automatic response message is prohibited.
 10. The system of claim 1,wherein the copy of the at least one message is communicated to at leastone of a target message box associated with the target communicationdevice or a forward target message box associated with the forwardtarget communication device when a message box option is selected inrelation to at least one of the target communication device or theforward target communication device.
 11. The system of claim 1, whereinthe one or more predefined message routing rules relate to at least oneof whether forwarding of the at least one message is prohibited by or inrelation to the originating communication device, whether forwarding ofthe at least one message is requested by or in relation to the targetcommunication device, whether forwarding of the at least one message isprohibited by or in relation to the forward target communication device,identifier associated with the originating communication device,identifier associated with the target communication device, identifierassociated with the forward target communication device, currentoperating state of the target communication device, current operatingstate of the forward target communication device, priority level of theat least one message, time of transmission of the at least one message,cost of forwarding the at least one message, whether the at least onemessage includes an attachment, or size of the at least one message. 12.The system of claim 1, wherein the at least one message is at least oneof a short message service (SMS) message, an enhanced message service(EMS) message, a multimedia messaging service (MMS) message, an instantmessage communicated via a communication device, or a Session InitiationProtocol (SIP) messages.
 13. A method, comprising: intercepting amessage sent from an originating mobile device to a target mobiledevice; and determining whether to forward a copy of the message fromthe target mobile device to the forward target mobile device based atleast in part on one or more predefined message routing rules.
 14. Themethod of claim 13, further comprising: identifying amessage-forwarding-allowance indicator in the message or informationassociated with the forward target mobile device that at least one ofdoes not indicate that forwarding the message to the forward targetmobile device is prohibited or indicates that forwarding the message tothe forward target mobile device is prohibited; at least one of:determining that the message is to be forwarded to the forward targetmobile device when the message-forwarding-allowance indicator is set toa defined message-forwarding-allowed value and information associatedwith the forward target mobile device does not indicate that forwardingthe message to the forward target mobile device is prohibited, ordetermining that the message is not to be forwarded to the forwardtarget mobile device when the message-forwarding-allowance indicator isset to a defined message-forwarding-prohibited value or informationassociated with the forward target mobile device indicates thatforwarding the message to the forward target mobile device isprohibited.
 15. The method of claim 13, further comprising: informationrelating to the one or more message routing rules or one or moremessaging options can be received; storing at least a portion of theinformation, in at least one of a first user profile associated with theoriginating mobile device, a second user profile associated with thetarget mobile device, or a third user profile associated with theforward target mobile device; and routing the message or the copy of themessage based at least in part on information stored in at least one ofthe first user profile, the second user profile, or the third userprofile.
 16. The method of claim 13, further comprising: identifyingthat a message is received by at least one of the target mobile deviceor the forward target mobile device; determining whether the at leastone of the target mobile device or the forward target mobile devicerequests to send an automatic response message to at least one of theoriginating mobile device or the target mobile device; and at least oneof: automatically sending the automatic response message to the at leastone of the originating mobile device or the target mobile device when anautomatic-response-allowance indicator is set to a value that indicatessending of the automatic response message is not prohibited, or notsending the automatic response message to the at least one of theoriginating mobile device or the target mobile device when anautomatic-response-allowance indicator is set to a value that indicatessending of the automatic response message is prohibited.
 17. The methodof claim 13, further comprising: receiving a selection indicatingwhether the copy of the message is to be delivered to a message boxassociated with at least one of the target mobile device or the forwardtarget mobile device; and at least one of: delivering the copy of themessage to the message box associated with the at least one of thetarget mobile device or the forward target mobile device when theselection indicates the copy of the message is to be delivered to themessage box associated with at least one of the target mobile device orthe forward target mobile device, or not delivering the copy of themessage to the message box associated with the at least one of thetarget mobile device or the forward target mobile device when theselection indicates the copy of the message is not to be delivered tothe message box associated with the at least one of the target mobiledevice or the forward target mobile device.
 18. The method of claim 13,wherein the one or more predefined message routing rules relate to atleast one of whether forwarding of the is prohibited by or in relationto the originating mobile device, whether forwarding of the message isrequested by or in relation to the target mobile device, whetherforwarding of the message is prohibited by or in relation to the forwardtarget mobile device, identifier associated with the originating mobiledevice, identifier associated with the target mobile device, identifierassociated with the forward target mobile device, current operatingstate of the target mobile device, current operating state of theforward target mobile device, priority level of the message, time oftransmission of the message, cost of forwarding the message, whether themessage includes an attachment, or size of the message.
 19. A system,comprising: a mobile communication device that is configured tocommunicate with at least one other mobile communication device in acommunication network; and at least one message management componentthat is configured to route a message to a target mobile communicationdevice and determine whether to forward a copy of the message to aforward target mobile communication device, in accordance with one ormore predefined message routing rules.
 20. The system of claim 19,wherein at least one of: the mobile communication device is the targetmobile communication device and is further configured to comprise the atleast one message management component, wherein the at least one messagemanagement component is further configured to route the copy of themessage to the forward target mobile communication device when the oneor more message routing rules specify that the copy of the message is tobe forwarded to the forward target mobile communication device, or notroute the copy of the message to the forward target mobile communicationdevice when the one or more message routing rules specify that the copyof the message is not to be forwarded to the forward target mobilecommunication device; the mobile communication device is the originatingmobile communication device and is further configured to send themessage to the target mobile communication device and comprise the atleast one message management component, wherein the at least one messagemanagement component is further configured to associate amessage-forwarding-allowance indicator that has a specified allowedvalue when forward of the copy of the message is not prohibited orassociate a message-forwarding-allowance indicator that has a specifiedprohibited value when forward of the copy of the message is prohibited;or the mobile communication device is the forward target mobilecommunication device and is further configured to comprise the at leastone message management component, wherein the at least one messagemanagement component is further configured to indicate whether the copyof the message is to be forwarded to, or is not to be forwarded to, theforward target mobile communication device.